Hi everyone,
Today is the last day for diablo-3 feature merges in Nova, as I will cut
the milestone branch early Tuesday morning. We have several features
that are very close to making it, and it would be great to have them in
the milestone so that they get wider testing... So please spend some
ti
Hi!
I have noticed that project quotas in nova could be stored and retrieved
even if the project doesn't exist. Indeed, nova database has no
restrictions, and the quotas' table could store quotas for projects with
arbitrary names even if there are no such projects in the projects' table.
Is i
Alessio Ababilov wrote:
> I have noticed that project quotas in nova could be stored and retrieved
> even if the project doesn't exist. Indeed, nova database has no
> restrictions, and the quotas' table could store quotas for projects with
> arbitrary names even if there are no such projects in the
Hi everyone.
nova-manage
/***
日本電信電話株式会社
NTT情報流通プラットフォーム研究所
情報流通プラットフォーム推進プロジェクト
プラットフォーム方式ＤＰ
田上 啓介
Tel (0422)59-6269FAX (0422)59-5652
〒180-8585 東京都武蔵野市緑町3-9-11
***/
Hi everyone,
Ubuntu is running Ubuntu Cloud Days (UCD) event *today* starting
16:00-UTC. This is a great way to learn about new development happening
in the server and cloud space for Ubuntu, as well as to ask questions,
connect to developers and make some more friends.
Technologies that wil
Hi Rangababu,
On Sat, Jul 23, 2011 at 12:58 PM, Rangababu Chakravarthula <
rb...@hexagrid.com> wrote:
> Couple of questions
> a) How can we address the max 4096 vlan's problem if each user want's a
> VLAN tagged network?
>
Currently, the notion of a VLAN is pretty central to the nova networking
All,
Rick Harris has produced some excellent code that adds functionality
for a local filesystem cache on Glance API nodes. I'd really like to
get this functionality into the D3 milestone release scheduled for
later this week. We need to cut the milestone release branch tomorrow,
and that means th
I don't see it as multiple projects, just as a set of modules:
openstack.common.config
openstack.common.deployment
openstack.common.logging
...
etc.
These are purely modules which help you create you're own OpenStack-compatible
project...all available through a single openstack-common project.
Would it better to break it down even further? I.e., instead of trying to
put ALL the common code into one project, create mini projects for
common-logging, common-configuration, etc. That would permit other
projects to adopt what they need, when they need it, rather than trying to
integrate the en
All,
I love the idea of having an openstack-common project. However, the prospect of
creating such a project is daunting and quite difficult.
It's my belief that standardizing/collecting common logic into a single module
will be beneficial to our current code-base and allow for future projects
Thats a better direction. Another way to think about this is to consider this
an extensible service framework. If we agree on lightweight code wrappers
(apis/modules) first with whatever "backend" each project uses, and then
migrate each of those areas to a common implementation, we can inject
If by mini-projects you mean small and separate projects, then I don't think
that makes sense.
All we need for this is a single project that contains submodules that don't
contain unnecessary dependencies on other submodules within the common project.
So lots of bite size pieces that can be us
I'm not sure if there is a fixable bug at this point. Projects are moving into
keystone, so there won't be any useful way for nova to verify whether a project
exists before creating a quota for it. As long as we are maintaining quotas in
nova, this will be the case. It may be that quotas even
+1
On Jul 25, 2011, at 11:59 AM, Devin Carlen wrote:
> If by mini-projects you mean small and separate projects, then I don't think
> that makes sense.
>
> All we need for this is a single project that contains submodules that don't
> contain unnecessary dependencies on other submodules wit
One thing that might be added would be dynamic module and class
loading. This has implications for flags/options and help output as
well. It is something nova does, and I suspect keystone and others
will need to do as well.
On Mon, Jul 25, 2011 at 2:59 PM, Devin Carlen wrote:
> If by mini-proje
Thank you Dan. Response below.
On Mon, Jul 25, 2011 at 11:36 AM, Dan Wendlandt wrote:
> Hi Rangababu,
>
> On Sat, Jul 23, 2011 at 12:58 PM, Rangababu Chakravarthula <
> rb...@hexagrid.com> wrote:
>
>> Couple of questions
>> a) How can we address the max 4096 vlan's problem if each user want's a
On Mon, Jul 25, 2011 at 3:08 PM, Rangababu Chakravarthula <
rb...@hexagrid.com> wrote:
> Thank you Dan. Response below.
>
> On Mon, Jul 25, 2011 at 11:36 AM, Dan Wendlandt wrote:
>
>> Hi Rangababu,
>>
>> On Sat, Jul 23, 2011 at 12:58 PM, Rangababu Chakravarthula <
>> rb...@hexagrid.com> wrote:
>>
17 matches
Mail list logo
