Hi,
On Fri, Jul 13, 2012 at 9:20 PM, Andrew Clay Shafer
a...@parvuscaptus.comwrote:
[...]
In this particular case, I chose option 1 under the following assumptions
(which may be wrong):
- the api for the end user would not change
- the code for the service is essentially the same,
I disagree with your last point, it is true if we look only into this
particular problem, but if you look into the whole ecosystem you'll realize
that the code removal of nova-volumes is not the only change from essex to
folsom.. if we had deprecated all other changes, this particular one would
Hi Everyone,
In light of the lively email threads the past couple of days I
thought it would be good to update the Cinder wiki page and point out
that it exists. In no way does it answer all of the
questions/concerns, however it does at least give a bit of an
introduction and at least offer some
Thanks John. This is very helpful.
On Jul 14, 2012, at 1:21 PM, John Griffith john.griff...@solidfire.com
wrote:
Hi Everyone,
In light of the lively email threads the past couple of days I
thought it would be good to update the Cinder wiki page and point out
that it exists. In no way
Apologies if this has already been proposed, but how about an option 3
(perhaps more accurately option 2.5):
We already have a process for maintaining code in one project and
occasionally copying it to another project. Namely, code is maintained
in openstack-common and then -- at appropriate
Emilien Macchi wrote:
My bad. I know for the future now.
Thank's and sorry for the mistake.
Just for future reference: filing a bug against Ubuntu packaging for a
given OpenStack package is done through:
https://bugs.launchpad.net/ubuntu/+source/nova
and click on Report a bug
or, for bugs
George Reese wrote:
How many years has it been? [...]
The answer to those questions is:
- 3
It's been 2 years, actually. Feels like 3 years, I know. We are still
maturing, obviously. But seeing the discussions we had at the last
design summit, I think that we are improving. We are now
I think I just figured out the problem. Please see:
https://bugs.launchpad.net/ceilometer/+bug/1024563
From: Doug Hellmann [doug.hellm...@dreamhost.com]
Sent: Friday, July 13, 2012 11:19 AM
To: TRAN, JOHN
Cc: 张家龙; Julien Danjou; openstack
Subject: Re:
Hi List,
I have a network problem while setting up essex. The instances on control
node can access internet, while instances on compute node cannot. I tcpdump
the ping traffic and found something weird. VM on compute node can send
ICMP request out and the src ip of the ICMP package is changed to
hi all
one of company here setup Stackato on OpenStack and in beta phase
any idea and comment regarding PAAS implementation in OpenStack
F
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe :
I think PaaSes should treat OpenStack much like running on top of EC2
or Rackspace or any other IaaS. They should try to be general agnostic
about the underlying infrastructure. I was glad to learn of Stackato,
it sounds like another open source PaaS to keep tabs on.
When you say PAAS
Hey frans,
There are a few that I can think of. Reddwarf (my project) [1], platform layer
[2], and heat [3]. They are all a bit different and I encourage u to look
around. I bet $$ there are more that I've forgotten, which I apoligize in
advance for :)
Sent from my digital shackles.
[1]
Hi,all.
Sorry for late reply.
Until now, I not test folsom. So, I`am not sure how it work in folsom .
The follow is my qpid config file:
http://pastebin.com/sBXm6k7z
And Doug writed set driver to
nova.openstack.common.notifier.rabbit_notifier,
while , I cannot found this
Title: quantal_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/quantal_folsom_nova_trunk/157/Project:quantal_folsom_nova_trunkDate of build:Sun, 15 Jul 2012 00:01:54 -0400Build duration:2 min 40 secBuild cause:Started by an SCM changeBuilt
Title: precise_folsom_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_nova_trunk/160/Project:precise_folsom_nova_trunkDate of build:Sun, 15 Jul 2012 00:01:54 -0400Build duration:3 min 11 secBuild cause:Started by an SCM changeBuilt
15 matches
Mail list logo
