Hello everyone,
Two regressions were detected in Cinder release candidate testing. We
respun a new release candidate to include the fixes for those issues in
the final Icehouse release. You can find links to the 2 bugs fixed and
the RC3 source tarball at:
Some notes:
Even though we use YAQL now our design is flexible enough to plug other ELs in.
If it tells you something in Amazon SWF a component that makes a decision about
a further route is called Decider.
This discussion about conditionals is surely important but it doesn’t matter
too much if
Hi there,
Currently,alarm_evaluator invoke ceilometerclient to get all assigned
alarms. and then, evaluate per alarm by get statistics, which will also
call ceilometerclient. this process is:
evaluator--ceilometerclient--ceilometer API--db.
If we use default option of evaluation_interval (60s),
Hi
I'm following link for opendaylight openstack integration..
http://networkstatic.net/opendaylight-openstack-integration-devstack-fedora-20/
I'm able to interact opendaylight controller with the stack using ml2
plugin and boot the VMs at the controller node and at compute node.
The problem
Since you have mentioned that, I'm kind of interested, who else is going to
benefit from this transition?
I'm asking because everyone tells me that it's essential for us to work
together, though my senses tells me that we are starting from different
prerequisites, targeting different use
On 15 Apr 2014, at 11:13, Joshua Harlow harlo...@yahoo-inc.com wrote:
Sure, its not the fully complete lazy_engine, but piece by piece we can get
there.
Did you make any estimations when it could happen? :)
Of course code/contributions are welcome, as such things will benefit more
than
On Mon, Apr 14, 2014 at 11:26:17AM -0500, Ben Nemec wrote:
tldr: I propose we use bash explicitly for all diskimage-builder
scripts (at least for the short-term - see details below).
This is something that was raised on my linting changes to enable
set -o pipefail. That is a bash-ism, so it
confirmed
On 04/15/2014 03:07 AM, Angus Salkeld wrote:
Hi all,
I'd like to announce my candidacy as a TC member.
A little about me:
I am a software developer at Rackspace (previously at Red Hat). I
started off my OpenStack
contributions with Heat (I started Heat with Steve Dake). I have
Team,
Following up on the yesterday’s community meeting I created an etherpad and
captured all the formal steps we need to make in order to consider Mistral PoC
ready [0]. Please take a look and comment and/or add other items that you think
I missed.
My expectation is to get all the items
Hi
On 15 April 2014 09:14, Daniel P. Berrange berra...@redhat.com wrote:
I supose that rewriting the code to be in Python is out of the
question ? IMHO shell is just a terrible language for doing any
program that is remotely complicated (ie longer than 10 lines of
I don't think it's out of
On Mon, Apr 14 2014, Doug Hellmann wrote:
Balancing Europe and Pacific TZs is going to be a challenge. I can't
go at 1800 or 1900, myself, and those are pushing a little late in
Europe anyway.
How about 1600?
Hi,
Just for reminder, the weekly meeting will be held today at 1500 UTC on
#openstack-meeting.
The agenda I can see for today is :
- Follow-up on previous actions
- Status on forklift efforts
- Juno summit design sessions
- open discussion
If you want to discuss about another topic, please
1600 UTC for me is ok. Later than that in Europe (Friday
afternoon/night) could be a problem.
Ghe Rivero
On 04/14/2014 10:56 PM, Doug Hellmann wrote:
That may work. Let's see what the team members in Europe say about the
proposed times.
Doug
On Mon, Apr 14, 2014 at 3:04 PM, Joshua Harlow
What I saw in this thread are several topics:
1) Is VM HA really relevant (in a cloud)?
This is the most difficult question to answer, because it really depends
on who you are talking to, who are the user community you are facing.
IMHO, for most web-based applications that are born to run on
Hello everyone!
I would like to try to solve this problem. I registered blueprint on this
topic
https://blueprints.launchpad.net/neutron/+spec/neutron-robust-db-migrationsand
I'm going to experiment with options to solve this. I'm welcome any
suggestions and ready to talk about it via IRC
On 11 April 2014 16:24, Eric Harney ehar...@redhat.com wrote:
I suppose I should also note that if the plans in this blueprint are
implemented the way I've had in mind, the main issue here about only
loading shares at startup time would be in place, so we may want to
consider these questions
On 14/04/14 19:51, Kevin Benton wrote:
Hi Mario,
Here is the problem:
import netaddr
p = netaddr.IPNetwork('2001:0db8::/64')
str(p)
'2001:db8::/64'
Now that you are converting CIDR strings to netaddr objects and back, it's
causing redundant info to be dropped. You will just have to
On 14 April 2014 19:51, James Penick pen...@yahoo-inc.com wrote:
We drive the ³VM=Cattle² message pretty hard. Part of onboarding a
property to our cloud, and allowing them to serve traffic from VMs is
explaining the transient nature of VMs. I broadcast the message that all
compute resources
Hi there,
I'd like to announce my candidacy as a TC member.
I'm a software engineer, and started contributing to OpenStack 2.5 years
ago. I've also been the Ceilometer PTL for the last year. And I've
actually already seated at the TC last year.
Within the TC, I'd like to focus on improving
Hi all,
I started working on the stack snapshot blueprint [1] and wrote a first series
of patches [2] to get a feeling of what's possible. I have a couple of related
design questions though:
* Is a stack snapshot independent of the stack? That's the way I chose for my
patches, you start with
confirmed
On 04/15/2014 01:13 PM, Julien Danjou wrote:
Hi there,
I'd like to announce my candidacy as a TC member.
I'm a software engineer, and started contributing to OpenStack 2.5 years
ago. I've also been the Ceilometer PTL for the last year. And I've
actually already seated at the TC
Hi.
I'd also like to announce my TC candidacy. I am currently a member of
the TC, and I would like to continue to serve.
I first started hacking on Nova during the Diablo release, with my
first code contributions appearing in the Essex release. Since then
I've hacked mostly on Nova and Oslo,
+1 to use bash as the default shell. So far, all major distros use bash
as the default one (except Debian which uses dash).
An about rewriting the code in Python, I agree that shell is complicated
for large programs, but writing anything command oriented in other than
shell is a nightmare. But
+1 for the use of /usr/share and keeping the compatibility for a couple
of releases.
Ghe Rivero
On 04/15/2014 03:30 AM, Clint Byrum wrote:
Excerpts from Ben Nemec's message of 2014-04-14 15:41:23 -0700:
Right now the os-*-config projects default to looking for their files in
/opt/stack, with
confirmed
On 04/15/2014 01:29 PM, Michael Still wrote:
Hi.
I'd also like to announce my TC candidacy. I am currently a member of
the TC, and I would like to continue to serve.
I first started hacking on Nova during the Diablo release, with my
first code contributions appearing in the
Julien, good inputs. I will make updates to the wiki after compiling feedback
from today's IRC
From: Julien Vey [vey.jul...@gmail.com]
Sent: Monday, April 14, 2014 3:14 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re:
Guys,
We have big and complicated structure of the project. And part of our
patchsets require additional actions before merge. Sometimes we need
approve from testers, sometimes we need merge requests in several repos at
the same time, sometimes we need updates of rpm repositories before merge.
Hi Stephen,
Thanks for a good summary. Some comments inline.
On Tue, Apr 15, 2014 at 5:20 AM, Stephen Balukoff sbaluk...@bluebox.netwrote:
So! On this front:
1. Does is make sense to keep filling out use cases in Samuel's document
above? I can think of several more use cases that our
Thanks Anna.
I've been following the issue so far, but I am happy to hand it over to you.
I think the problem assessment is complete, but if you have more questions
ping me on IRC.
Regarding the solution, I think we already have a fairly wide consensus on
the approach.
There are however a few
Hi all!
I'd like to announce my candidacy to serve as a TC member.
About me:
I'm a software engineer at Red Hat, and have been working full-time on
OpenStack for the last two years. I've been heavily involved with the Heat
project since before it was incubated, served as PTL for the Havana
On Mon, Apr 14, 2014 at 06:30:59PM -0700, Clint Byrum wrote:
Excerpts from Ben Nemec's message of 2014-04-14 15:41:23 -0700:
Right now the os-*-config projects default to looking for their files in
/opt/stack, with an override env var provided for other locations. For
packaging purposes
IIRC implementing something like this had been discussed quite a while back.
I think we discussed the possibility of using web hooks and a defined
api/payload in place of the SNS/SQS type stuff. I don't think it ever made
it to the backlog, but I'd be happy to discuss further design and maybe
confirmed
On 04/15/2014 02:04 PM, Steven Hardy wrote:
Hi all!
I'd like to announce my candidacy to serve as a TC member.
About me:
I'm a software engineer at Red Hat, and have been working full-time on
OpenStack for the last two years. I've been heavily involved with the Heat
On Mon, Apr 14, 2014 at 07:24:57PM +0100, Chris Jones wrote:
Hi
Apart from special cases like the ramdisk's /init, which is a script that
needs
to run in busybox's shell, everything should be using bash. There's no point
us
tying ourselves in knots trying to achieve POSIX compliance for
Hi Stackers,
I've known OpenStack since it was a baby, and I've watched it grow to
the teenager it is today -- pimples and all. I hope to help guide it
along its way to adulthood by serving on the Technical Committee.
Besides developing on a number of core and ecosystem OpenStack projects,
I've
confirmed
On 04/15/2014 02:18 PM, Jay Pipes wrote:
Hi Stackers,
I've known OpenStack since it was a baby, and I've watched it grow to
the teenager it is today -- pimples and all. I hope to help guide it
along its way to adulthood by serving on the Technical Committee.
Besides developing
On 15/04/14 11:05 +0200, Julien Danjou wrote:
On Mon, Apr 14 2014, Doug Hellmann wrote:
Balancing Europe and Pacific TZs is going to be a challenge. I can't
go at 1800 or 1900, myself, and those are pushing a little late in
Europe anyway.
How about 1600?
- Original Message -
From: Chris Jones c...@tenshu.net
To: openst...@nemebean.com, OpenStack Development Mailing List (not for
usage questions)
openstack-dev@lists.openstack.org
Sent: Monday, April 14, 2014 2:24:57 PM
Subject: Re: [openstack-dev] [tripleo] /bin/bash vs. /bin/sh
Thanks a lot, folks!
Eugene.
On Tue, Apr 15, 2014 at 2:55 AM, Stephen Balukoff sbaluk...@bluebox.netwrote:
I've also added our L7 feature usage data on a new tab.
On Mon, Apr 14, 2014 at 3:03 PM, Prashanth Hari hvpr...@gmail.com wrote:
Hi,
We have updated the operators data -
Sorry, I’m not quite clear about it yet.
I’m trying to find a way that heat controls the flow but not the nova scheduler.
发件人: Henrique Truta [mailto:henriquecostatr...@gmail.com]
发送时间: 2014年4月14日 21:39
收件人: OpenStack Development Mailing List (not for usage questions)
主题: Re: [openstack-dev]
Hey there,
I've got a quick question about the RabbitMQ exchanges. We are writing
listeners
for the RabbitMQ exchanges. The basic information about the tasks like
compute.instance.create.[start|stop] etc. as stored in the 'payload'
attribute of the
json message are my concern at the moment.
Does
Hello openstackers,
MagnetoDB community is proud to announce the release
of magnetodb-2.0.2 milestone.
It is publicly available here
https://pypi.python.org/pypi/magnetodb/2.0.2
http://tarballs.openstack.org/magnetodb/
The version contains following features and major fixes
+ devstack
On Tue, Apr 15, 2014 at 7:03 AM, Salvatore Orlando sorla...@nicira.com wrote:
Thanks Anna.
I've been following the issue so far, but I am happy to hand it over to you.
I think the problem assessment is complete, but if you have more questions
ping me on IRC.
Regarding the solution, I think
On 04/15/2014 09:07 AM, George Monday wrote:
Hey there,
I've got a quick question about the RabbitMQ exchanges. We are writing
listeners
for the RabbitMQ exchanges. The basic information about the tasks like
compute.instance.create.[start|stop] etc. as stored in the 'payload'
attribute of
On 04/14/2014 09:30 PM, Clint Byrum wrote:
Excerpts from Ben Nemec's message of 2014-04-14 15:41:23 -0700:
Right now the os-*-config projects default to looking for their files in
/opt/stack, with an override env var provided for other locations. For
packaging purposes it would be nice if
+1 to using bash, the argument about not keeping POSIX compliance for
the sake of it makes sense to me.
On 04/15/2014 07:31 AM, Ghe Rivero wrote:
+1 to use bash as the default shell. So far, all major distros use bash
as the default one (except Debian which uses dash).
An about rewriting the
On 04/15/2014 10:07 AM, George Monday wrote:
Hey there,
I've got a quick question about the RabbitMQ exchanges. We are writing
listeners
for the RabbitMQ exchanges. The basic information about the tasks like
compute.instance.create.[start|stop] etc. as stored in the 'payload'
attribute
Hi again, Divakar, sorry for the delayed response!
On Wed, 2014-04-09 at 14:52 +, Nandavar, Divakar Padiyar wrote:
Hi Jay, Managing multiple clusters using the Compute Proxy is not new
right? Prior to this nova baremetal driver has used this model
already.
Yes, unfortunately. However,
Hey there,
thanks for the input.
@Russel
My bad, sorry. Yes I was talking about notifications.
@Sandy
I'll have a look into the links provided. Thanks.
I guess we can consider this closed.
Cheers,
George
On Tue, Apr 15, 2014 at 3:40 PM, Sandy Walsh sandy.wa...@rackspace.comwrote:
On
Hi.
I would like to announce my TC candidacy.
I work full time as a Software Developer on OpenStack at Rackspace,
part of the team working on Rackspace Cloud Servers, Rackspace's
public cloud. I am a Nova core reviewer, a member of nova-drivers,
leader of the XenAPI Nova sub-team, and the Nova
Hi Folks,
Sorry for being a tad slow on the uptake here, but I'm trying to understand the
sequence of updates required to move from a system that doesn't have external
events configured between Neutron and Nova and one that does (The new
nova-specs repo would have captured this as part of
confirmed
On 04/15/2014 04:03 PM, John Garbutt wrote:
Hi.
I would like to announce my TC candidacy.
I work full time as a Software Developer on OpenStack at Rackspace,
part of the team working on Rackspace Cloud Servers, Rackspace's
public cloud. I am a Nova core reviewer, a member of
If feels like the right sequence is:
- Deploy the new code in Nova and at the same time set
vif_plugging_is-fatal=False, so that Nova will wait for Neutron, but
will still continue if the event never turns up (which is kind of like
the code was before, but with a wait)
Yes, but
Sorry if you get this twice.
Since summit is approaching quickly, I wanted to see if anyone had interest
in forming a meetup for 3rd party testing. This would be a group for
helping the project cores by helping ourselves and hopefully improving
overall CI rollout.
Some topics to discuss: I'd
On Mon, 2014-04-14 at 14:53 -0400, Doug Hellmann wrote:
Balancing Europe and Pacific TZs is going to be a challenge. I can't
go at 1800 or 1900, myself, and those are pushing a little late in
Europe anyway.
How about 1600?
The NetApp driver uses NetApp specific API calls to implement the actual
cloning of the file. You could probably generalize it by implementing the
keeping of a cached image file on the destination share for future copies,
and then implement a standard copy file method that could be overloaded
by
On 04/15/2014 10:20 AM, Kurt Taylor wrote:
Sorry if you get this twice.
Since summit is approaching quickly, I wanted to see if anyone had interest
in forming a meetup for 3rd party testing. This would be a group for
helping the project cores by helping ourselves and hopefully improving
Humans make mistakes... all the time. Let's think how we can automate this
to have appropriate Jenkins check. In this particular case, we could do the
following:
a) make it work in progress if we still unsure on some deps
b) can we have smoke test which would check that master node builds, and
Ilya, here is link to the bug created:
https://bugs.launchpad.net/fuel/+bug/1308104
On Sun, Apr 13, 2014 at 8:53 AM, Vladimir Kuklin vkuk...@mirantis.comwrote:
Ilya, thank you for pointing this out. Obviously we will add it into fuel
manifests.
10 апр. 2014 г. 19:43 пользователь Ilya
On Apr 13, 2014, at 11:58 PM, Michael Still mi...@stillhq.com wrote:
First off, thanks for electing me as the Nova PTL for Juno. I find the
outcome of the election both flattering and daunting. I'd like to
thank Dan and John for running as PTL candidates as well -- I strongly
believe that a
On 04/15/2014 03:16 AM, Qiming Teng wrote:
What I saw in this thread are several topics:
1) Is VM HA really relevant (in a cloud)?
This is the most difficult question to answer, because it really depends
on who you are talking to, who are the user community you are facing.
IMHO, for most
On 04/15/2014 06:03 AM, Jiangying (Jenny) wrote:
Sorry, I'm not quite clear about it yet.
I'm trying to find a way that heat controls the flow but not the nova
scheduler.
Heat doesn't control flow. Heat expects a scheduler is built into
whatever service it is consuming for resource
On 04/15/2014 11:01 AM, Brian Elliott wrote:
* specs review. The new blueprint process is a work of genius, and I
think its already working better than what we've had in previous
releases. However, there are a lot of blueprints there in review, and
we need to focus on making sure these get
So every developer should manually mark every such review as WIP? And
remove this flag only when everyone agreed to merge? This will require
additional actions in 50% of fuel-web and 100% of fuel-main reviews.
Developers make mistakes too.
Let's just be more accurate.
On Tue, Apr 15, 2014 at
I know alembic is designed to be global, but could we extend it to track
multiple histories for a given database. In other words, various branches for
different namespaces on a single database. Would this feature ameliorate the
issues?
Amir
On Apr 15, 2014, at 8:24 AM, Kyle Mestery
Hi Everyone,
Here are the minutes from today’s Hyper-V Meeting.
Minutes:
http://eavesdrop.openstack.org/meetings/hyper_v/2014/hyper_v.2014-04-15-16.02.html
Minutes (text):
http://eavesdrop.openstack.org/meetings/hyper_v/2014/hyper_v.2014-04-15-16.02.txt
Log:
Anita Kuno ante...@anteaya.info wrote on 04/15/2014 09:41:17 AM:
On 04/15/2014 10:20 AM, Kurt Taylor wrote:
Sorry if you get this twice.
Since summit is approaching quickly, I wanted to see if anyone had
interest
in forming a meetup for 3rd party testing. This would be a group for
Is there a plan to get Hyper-V CI working better? It looks like it is
failing significantly more frequently then Jenkins.
http://www.rcbops.com/gerrit/reports/nova-cireport.html
On Tue, Apr 15, 2014 at 9:25 AM, Peter Pouliot ppoul...@microsoft.comwrote:
Hi Everyone,
Here are the minutes
On 04/15/2014 12:34 PM, Kurt Taylor wrote:
Anita Kuno ante...@anteaya.info wrote on 04/15/2014 09:41:17 AM:
On 04/15/2014 10:20 AM, Kurt Taylor wrote:
Sorry if you get this twice.
Since summit is approaching quickly, I wanted to see if anyone had
interest
in forming a meetup for 3rd
Meeting minutes:
http://eavesdrop.openstack.org/meetings/neutron_ipv6/2014/neutron_ipv6.2014-04-15-14.00.html
See you next week!
--
Sean M. Collins
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
I think we agree on the lazy execution model. At least at a high-level, I'd
rather not agree on the API's that are exactly exposed until there is an
implementation since I've found that agreeing to any type of API's before there
is the needed groundwork to make it happen is pretty useless and a
Well Ivan afaik is thinking through it, but being a community project its not
exactly easy to put estimations or timelines on things (I don't control Ivan,
or others).
Likely faster if u guys want to get involved.
-Josh
From: Renat Akhmerov rakhme...@mirantis.commailto:rakhme...@mirantis.com
Another +1 for using bash. Sounds like an easy win.
On 15/04/14 12:31, Ghe Rivero wrote:
+1 to use bash as the default shell. So far, all major distros use bash
as the default one (except Debian which uses dash).
An about rewriting the code in Python, I agree that shell is complicated
for large
On Apr 14, 2014, at 11:54 AM, Salvatore Orlando
sorla...@nicira.commailto:sorla...@nicira.com wrote:
1) Specify that all migrations must run for every plugin (*) unless they are
really introducing schemas which are specific to a particular technology (such
as uuid mappings between neutron
On 04/15/2014 11:42 AM, Russell Bryant wrote:
On 04/15/2014 11:01 AM, Brian Elliott wrote:
* specs review. The new blueprint process is a work of genius, and I
think its already working better than what we've had in previous
releases. However, there are a lot of blueprints there in review, and
I'm trying to modify a 3rd party test setup to use zuul, but I'm seeing the
following error when I start up the zuul server:
===
2014-04-15 09:09:18,910 ERROR gerrit.GerritWatcher: Exception on ssh event
stream:
Traceback (most recent call last):
File
I've been watching the nova process, and I think its working out well
- it certainly addresses:
- making design work visible
- being able to tell who has had input
- and providing clear feedback to the designers
I'd like to do the same thing for TripleO this cycle..
I'm thinking we can just
Hello all,
I’d like to announce my candidacy for the Technical Committee election.
I was one of the original authors of the Nova project and served as
its PTL for the first two years that the position existed. I have also
been on the Technical Comittee since its inception. I was also recently
FWIW: we are using bash in devstack if we were going to try to make it
POSIX bourne shell (or whatever /bin/sh is) it would have been a huge pain.
On Tue, Apr 15, 2014 at 1:25 PM, Dougal Matthews dou...@redhat.com wrote:
Another +1 for using bash. Sounds like an easy win.
On 15/04/14 12:31,
confirmed
On 04/15/2014 08:45 PM, Vishvananda Ishaya wrote:
Hello all,
I’d like to announce my candidacy for the Technical Committee election.
I was one of the original authors of the Nova project and served as
its PTL for the first two years that the position existed. I have also
been
Hi Kanzhe,
First off, thank you for showing interest in discussing this proposal!
I’m not fully sure if I understood your point. Could you elaborate a bit more
on the L1, L2, L3 part?
Regarding the traffic steering API, as I see it the Neutron port is the virtual
counterpart of the network
Just wanted to confirm what Sean said -- as someone who just joined the
OpenStack community last
year, going to implement a vaguely worded blueprint and then having the code
review be derailed
with people saying well, you probably should be using this completely
different design is fairly
On 15/04/14 14:31, Mike Spreitzer wrote:
It appears that in Fedora 19 and 20 the Wordpress examples need to
install different packages than in every other release (see my debugging
in https://review.openstack.org/#/c/87065/). I just got a complaint
from Heat validation that I can't do this:
On 04/15/2014 11:44 AM, Robert Collins wrote:
I've been watching the nova process, and I think its working out well
- it certainly addresses:
- making design work visible
- being able to tell who has had input
- and providing clear feedback to the designers
I'd like to do the same thing
Excerpts from Ben Nemec's message of 2014-04-14 09:26:17 -0700:
tldr: I propose we use bash explicitly for all diskimage-builder scripts
(at least for the short-term - see details below).
This is something that was raised on my linting changes to enable set -o
pipefail. That is a
Excerpts from Ghe Rivero's message of 2014-04-15 04:31:19 -0700:
+1 to use bash as the default shell. So far, all major distros use bash
as the default one (except Debian which uses dash).
An about rewriting the code in Python, I agree that shell is complicated
for large programs, but writing
Exactly. Even if operators/users only comment with a +0, it's already
flushed out a lot of good details on several blueprints.
Thanks!
Matt
On 4/15/14 2:38 PM, Tim Bell tim.b...@cern.ch wrote:
+2
I think that there is also a need to verify the user story aspect. One of
the great things with
On 04/15/2014 01:44 PM, Robert Collins wrote:
I've been watching the nova process, and I think its working out well
- it certainly addresses:
- making design work visible
- being able to tell who has had input
- and providing clear feedback to the designers
I'd like to do the same thing
Zane Bitter zbit...@redhat.com wrote on 04/15/2014 03:29:03 PM:
On 15/04/14 14:31, Mike Spreitzer wrote:
It appears that in Fedora 19 and 20 the Wordpress examples need to
install different packages than in every other release (see my
debugging
in https://review.openstack.org/#/c/87065/).
On Mon, Apr 14, 2014 at 8:02 AM, Elizabeth Krumbach Joseph
l...@princessleia.com wrote:
Hi everyone,
The OpenStack Infrastructure (Infra) team is hosting our weekly
meeting tomorrow, Tuesday April 15th, at 19:00 UTC in
#openstack-meeting
Meeting logs and minutes:
Minutes:
+1, I think it's a better medium for conversations than blueprints or wikis.
I'm also +1 to a tripleo-specs repo, but that's less me having a problem
with using incubator and more my OCD.
On 04/15/2014 03:43 PM, Monty Taylor wrote:
On 04/15/2014 11:44 AM, Robert Collins wrote:
I've been
On 04/15/2014 02:44 PM, Clint Byrum wrote:
Excerpts from Ben Nemec's message of 2014-04-14 09:26:17 -0700:
tldr: I propose we use bash explicitly for all diskimage-builder scripts
(at least for the short-term - see details below).
This is something that was raised on my linting changes to
On Mon, Apr 14, 2014 at 7:06 PM, Stefano Maffulli stef...@openstack.org wrote:
On 04/14/2014 06:58 AM, Michael Still wrote:
First off, thanks for electing me as the Nova PTL for Juno.
Congratulations Michael.
* I promised to look at mentoring newcomers. The first step there is
working out
On Fri, Apr 11, 2014 at 8:40 AM, Anne Gentle a...@openstack.org wrote:
I'd love to see consolidation as I've tried to keep up nova dev docs for
example, and with all the options it's tough to test and maintain one for
docs. Go for it.
Nova isn't the only project that uses devstack, so
On Fri, Apr 11, 2014 at 11:24 AM, Sean Dague s...@dague.net wrote:
On 04/11/2014 11:38 AM, Greg Lucas wrote:
Sean Dague wrote:
Maybe it would be good to get an ad-hoc IRC meeting together to figure
out what the must have features are that inspired everyone to write
these. If we can come
On 15/04/14 15:57, Mike Spreitzer wrote:
Zane Bitter zbit...@redhat.com wrote on 04/15/2014 03:29:03 PM:
On 15/04/14 14:31, Mike Spreitzer wrote:
It appears that in Fedora 19 and 20 the Wordpress examples need to
install different packages than in every other release (see my
debugging
Hi Steven et al.
2014-04-15 17:01 GMT+02:00 Steven Dake sd...@redhat.com:
Qiming,
If you read my original post on this thread, it outlines the current
heat-core thinking, which is to reduce the scope of this resource from the
Heat resources since it describes a workflow rather then an
On Sun, Apr 6, 2014 at 6:06 AM, Christopher Yeoh cbky...@gmail.com wrote:
On Sat, Apr 5, 2014 at 10:17 PM, Joshua Hesketh
joshua.hesk...@rackspace.com wrote:
Hi Chris,
Thanks for your input.
On 4/5/14 9:56 PM, Christopher Yeoh wrote:
On Sat, 5 Apr 2014 15:16:33 +1100
Joshua Hesketh
Hi folks,
In Icehouse there were attempts to apply Provider Framework ('Service Type
Framework') approach to VPN and Firewall services.
Initially Provider Framework was created as a simplistic approach of
allowing user to choose service implementation.
That approach definitely didn't account for
Hi Nova developers:
I have a question around the new nova-specs gerrit repository. We're
implementing the same thing in Neutron for Juno (I'm hoping to make
this live tomorrow), but I had a few quick questions so I can build on
your experience with this so far:
1. Did you implement any sort of
1 - 100 of 147 matches
Mail list logo
