Hi
I am working on https://review.openstack.org/#/c/61359/
and its purpose is to include reason in the exception message when claim
failed
There are 2 choice for the reasons returned, one is to
return all reasons (e.g both cpu and mem can't be claimed successf
On 14/01/14 16:33 -0600, Ben Nemec wrote:
On 2014-01-14 15:26, Doug Hellmann wrote:
In the release meeting today, Russell proposed that we at least include the
hash of the HEAD when the merge is done, to indicate how far along the oslo
changes are. More detail is obviously better.
On 2014/13/01 13:15, Ladislav Smola wrote:
The usage of roles is new metric which doesn't exist. It is the most
consumed HW resource (which means if CPU is consumed by 60 % and RAM
or disk are less, then the role usage is 60 %). It would be great to
have such a metric from Ceilometer. However, I
On 2014/13/01 12:20, Ladislav Smola wrote:
[snip of larger amount of text]
- When on the change deployments screen, after making a change but not
yet applying it, how are the projected capacity changes calculated?
I believe we wanted to make just simple algorithm, that was considering,
that ad
1) Check for an already deleted server before deleting any. This is
related to stack convergence:
https://blueprints.launchpad.net/heat/+spec/stack-convergence
This will allow users to just delete a server they want to delete,
and then update the template to reflect reality.
2) Allow resources
I'm echoing markwash's concern. At least for Glance, I didn't see a strong
justification or function gap to push us switching to Pecan. So I prefer to
implement it in next major version and pending it in Glance v2.
Thanks & Best regards,
Fei Long Wang (王飞龙)
Hi, Devananda
On Wed, Jan 15, 2014 at 8:19 AM, Devananda van der Veen <
[email protected]> wrote:
>
>
> On Tue, Jan 14, 2014 at 6:28 AM, Alexander Gordeev
> wrote:
>
>>
>>- Secondly, virsh has some performance issues if you deal with >30
>>VMs (it is not our case for now but who kn
On 14/01/14 14:48 -0500, Doug Hellmann wrote:
I've spent some time over the past day or two looking at the dependencies
between modules in the oslo incubator, trying to balance the desire to have a
small number of libraries with themes that make sense and the need to eliminate
circular dependenci
Sergey Lukjanov wrote:
> I think that in case of adding additional meeting rooms, we'll need to
> avoid disparity between them in names. For example, currently we have a
> lot of folks in #os-meeting and not so many in #os-meeting-alt, if we'll
> have #os-meeting-alt-2 then we'll have even less fol
On 2014/13/01 16:45, Jiří Stránský wrote:
[snip]
The other approach is just to scale the number of nodes in a role and
let system decide the best match (which node profile is chosen will be
decided on the best fit, probably).
Hmm i'm not sure i understand - what do you think by "best fit" here?
Hi,
does anyone knows if the multi-node environnement is targeted by the
openstack-infra team?
On Tue, Jan 14, 2014 at 6:22 PM, Anita Kuno wrote:
> On 01/14/2014 11:34 AM, Kyle Mestery wrote:
>> Given the Tempest Sprint in Montreal, I still think we should have this
>> meeting
>> on IRC.
> Sho
Thanks Danilel.
I tried adding the iptable rules but I am still getting error 500 with
docker push
I have added the container logs and iptables output at [1]
[1] http://paste.openstack.org/show/61251/
Best Regards,
Swapnil
On Mon, Jan 13, 2014 at 7:28 PM, Daniel Kuffner wrote:
> Hello,
>
>
On 15/01/14 18:11 +0800, Fei Long Wang wrote:
I'm echoing markwash's concern. At least for Glance, I didn't see a strong
justification or function gap to push us switching to Pecan. So I prefer to
implement it in next major version and pending it in Glance v2.
Thanks & Best regards,
Fei Long Wan
On 01/15/2014 10:53 AM, Jaromir Coufal wrote:
On 2014/13/01 13:15, Ladislav Smola wrote:
The usage of roles is new metric which doesn't exist. It is the most
consumed HW resource (which means if CPU is consumed by 60 % and RAM
or disk are less, then the role usage is 60 %). It would be great to
Hi Alexei:
Thanks for your information. IMO, if you remove them, the
file tools/nova.bash_completion should be removed too, right?
If so, I'm willing to participate with you to do this.
2014/1/15 Alexei Kornienko
> Hello Lingxian,
>
> Actually I'm planning to remove both of them.
>
> I'm wo
On Tue, Jan 14 2014, Ben Nemec wrote:
> It would be nice to get lockutils graduated to solve some of the issues
> mentioned in the oslo.db section, but I believe we do have an
> outstanding question regarding its behavior without lock_path being set.
> I think Clint was on board with Sean's propos
On 15/01/14 11:28 +0100, Thierry Carrez wrote:
Sergey Lukjanov wrote:
I think that in case of adding additional meeting rooms, we'll need to
avoid disparity between them in names. For example, currently we have a
lot of folks in #os-meeting and not so many in #os-meeting-alt, if we'll
have #os-m
On 2014-01-14 16:04, Collins, Sean wrote:
Can we get the -1 from Tail-F cleared from this review?
https://review.openstack.org/#/c/56184/17
I've been trying to do this but it fails.
Possibly because it is 'Abandoned' ?
See below:
$ ssh -p 29418 ncsopenstack gerrit review -m '"Clearing out wro
Hello All.
As for lockutils - a few days ago I wondered why we used custom oslo module
instead of lockfile library [1]. AFAIK, it must be due to this bug [2]
(please fix me, if I wrong).
This library is available on github [3] and there is a pull-request fixing
the bug [4], but unfortunately it h
On Tue, Jan 14, 2014 at 8:06 PM, Sean Dague wrote:
On 01/14/2014 05:17 AM, Christopher Yeoh wrote:
> > On Mon, Jan 13, 2014 at 10:38 PM, Sean Dague
> This skirts the run time issue, but using twice as many resources. It
> doesn't however address the fact that real effort goes into maintaining
>
Agreed that -meeting3 is ok.
BTW my main concern is a process of managing overlaps between projects
meetings time, that'll harder and harder with increasing number of meeting
rooms.
On Wed, Jan 15, 2014 at 3:32 PM, Flavio Percoco wrote:
> On 15/01/14 11:28 +0100, Thierry Carrez wrote:
>
>> Ser
Agreed Kevin.
This will make the inconsistencies disappear from the API. On the other
hand, this would be a bit like sweeping the dust under the carpet as those
inconsistencies will still exist in the data model.
Yong, the issue with arbitrary changes to device_id and device_owner is
real and I t
On Wed, Jan 15, 2014 at 4:40 AM, Flavio Percoco wrote:
> On 14/01/14 16:33 -0600, Ben Nemec wrote:
>
>> On 2014-01-14 15:26, Doug Hellmann wrote:
>>
>>In the release meeting today, Russell proposed that we at least
>> include the
>>hash of the HEAD when the merge is done, to indicate how
Logically, the port is really an alias for the external port of the router,
rather than being just detached. I'm not sure this adds much to the
discussion, but clearly that's where its traffic goes and is terminated.
>From past experience (don't ask) weird things happen if you start creating
your
On Mon, Jan 13, 2014 at 4:47 AM, Jaromir Coufal wrote:
>> - For editing a role, does it make a new image with the changes to what
>> services are deployed each time it's saved?
>
> So, there are two things - one thing is provisioning image. We are not
> dealing with image builder at the moment. So
On Jan 13, 2014 3:42 PM, "Lyle, David" wrote:
>
> With all the warranted meeting time shuffling that has been happening
recently, and the addition of so many projects and sub-teams, the meeting
calendar for #openstack-meeting and #openstack-meeting-alt [1] is
relatively full. So recently, when tr
On 15/01/14 07:44 -0500, Doug Hellmann wrote:
[...]
I don't see a problem with doing that, but I'm not clear on where we're
including the hash. In the file itself, in a separate file, and/or in
the
commit message?
Even if we do no more automation, having the
I'll start by laying out how I see editing or updating nodes working
in TripleO without Tuskar:
To do my initial deployment:
1. I build a set of images for my deployment for different roles. The
images are different based on their role, and only contain the needed
software components to accomplis
Hi all,
I've been working on a patch to ensure that all tempest tests are able to
handle rate limiting errors with automatic retries [0].
API tests already implement retries, however scenario tests don't, the main
reason being that scenario tests rely on the official python bindings, most
of w
On 2014年01月14日 20:04, Ken'ichi Ohmichi wrote:
> Hi,
>
> 2014/1/14 Alex Xu :
>> +1 for drop xml. But if we can't drop it, can we think about use
>> XMLDictSerializer instead of XmlTemplate? We spend a lot of time to maintain
>> XmlTemplate, and it make xml
>> format inconsistent(some of resouce's at
Is the impact of dropping XML understood for the users of the OpenStack APIs ?
Tim
> -Original Message-
> From: Alex Xu [mailto:[email protected]]
> Sent: 15 January 2014 14:33
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [nova] [
On 01/15/2014 08:44 AM, Tim Bell wrote:
> Is the impact of dropping XML understood for the users of the OpenStack APIs ?
That was the rationale for the openstack@ thread on this as well.
I believe the impact on users will be more reliable Nova API for users.
It will also mean a more clear surface
Joe Gordon wrote:
>> [1]
> https://www.google.com/calendar/ical/[email protected]/public/basic.ics
>
> Is this calendar periodically pruned of dead meetings (for some
> definition of dead)? If not doing so may free up a few slots.
It's kept in sync with the Meet
On Tue, Jan 14, 2014 at 6:00 PM, Michael Still wrote:
> On Wed, Jan 15, 2014 at 9:27 AM, Ben Nemec wrote:
>
> > It would be nice to get lockutils graduated to solve some of the issues
> > mentioned in the oslo.db section, but I believe we do have an outstanding
> > question regarding its behavio
On Wed, Jan 15, 2014 at 5:24 AM, Flavio Percoco wrote:
> On 14/01/14 14:48 -0500, Doug Hellmann wrote:
>
>> I've spent some time over the past day or two looking at the dependencies
>> between modules in the oslo incubator, trying to balance the desire to
>> have a
>> small number of libraries wi
Hi fellow OpenStackers
Does anyone have any recommendations on open source tools for disk erasure/data
destruction software. I have so far looked at DBAN and disk scrubber and was
wondering if ironic team have some better recommendations?
BR
Alan
___
Just a quick reminder that the weekly OpenStack QA team IRC meeting will be
tommorrow Thursday, January 16th at 17:00 UTC in the #openstack-meeting
channel.
The meeting agenda can be found here:
https://wiki.openstack.org/wiki/Meetings/QATeamMeeting
Anyone is welcome to add an item to the agenda.
Hi there!
Recently I've decided to fix situation with Murano's dashboard and move all
Murano-specific django settings into a separate file (previously they were
appended to
/usr/share/openstack-dashboard/openstack_dashboard/settings.py). But, as I
knew, /etc/openstack_dashboard/local_settings.py i
On Wed, Jan 15, 2014 at 6:51 AM, Victor Sergeyev wrote:
> Hello All.
>
> As for lockutils - a few days ago I wondered why we used custom oslo
> module instead of lockfile library [1]. AFAIK, it must be due to this bug
> [2] (please fix me, if I wrong).
>
> This library is available on github [3] a
If you are working on linux system following can help you:
dd if=/dev/urandom of=/dev/sda bs=4k
:)
Best Regards,
On 01/15/2014 04:31 PM, Alan Kavanagh wrote:
Hi fellow OpenStackers
Does anyone have any recommendations on open source tools for disk
erasure/data destruction software. I have s
Sorry for this not threading properly. I had set the Mailman config to filter
on Neutron topic but it ended up filtering out everything so I only saw
responses by looking at the archive. I removed the filter in Mailman and will
have to filter locally on my end. But I don't have any of the origin
On 15/01/14 15:30, Timur Sufiev wrote:
> Recently I've decided to fix situation with Murano's dashboard and move
> all Murano-specific django settings into a separate file (previously
> they were appended to
> /usr/share/openstack-dashboard/openstack_dashboard/settings.py). But, as
> I knew, /etc/o
On Jan 9, 2014, at 4:41 AM, Jay Lau wrote:
> My bad, the image cannot be viewed.
>
> Upload again.
>
> Thanks,
>
> Jay
>
>
> 2014/1/9 Jay Lau
> Hi,
>
> Now when using OpenStack dashboard to launch a stack, we need to first import
> the template then create the stack, but there is no way
I am also perplexed about the ports backing floating ips. when plugin is
selected OVS or LB, the ip address belonging to a port backing that floating
ip is really set on VIF of 'qg-' , what is the port real action?
At 2014-01-15 07:50:36,"Salvatore Orlando" wrote:
TL;DR;
I have been loo
> -Original Message-
> From: James Slagle [mailto:[email protected]]
> Sent: Wednesday, January 15, 2014 5:52 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [TripleO] [Tuskar] Deployment Management
> section - Wireframes
> This doe
Swapnil Kulkarni writes:
> Thanks Danilel.
>
> I tried adding the iptable rules but I am still getting error 500 with
> docker push
>
> I have added the container logs and iptables output at [1]
>
> [1] http://paste.openstack.org/show/61251/
>
> Best Regards,
> Swapnil
Swapnil,
I think this is b
On Wed, Jan 15, 2014 at 6:42 PM, Alexei Kornienko <
[email protected]> wrote:
> If you are working on linux system following can help you:
>
> dd if=/dev/urandom of=/dev/sda bs=4k
>
I would not recommend that as /dev/urandom is real slow (10-15 MB/s).
--
Best regards,
Oleg Gelbukh
>
>
>
> I think this is because your OS_GLANCE_URL and OS_AUTH_URL are set to
> 127.0.0.1, and that address inside of the docker container is different
> than the address outside (e.g. on the host itself). If you have glance
> and keystone running on a non-localhost address, then the traffic inside
On 1/15/14 9:01 AM, "Liz Blanchard" wrote:
>
>On Jan 9, 2014, at 4:41 AM, Jay Lau wrote:
>
>
>My bad, the image cannot be viewed.
>
>
>Upload again.
>
>
>
>Thanks,
>
>
>Jay
>
>
>
>2014/1/9 Jay Lau
>
>Hi,
>
>
>Now when using OpenStack dashboard to launch a stack, we need to first
>import the te
On 2014-01-15 05:51, Victor Sergeyev wrote:
> Hello All.
>
> As for lockutils - a few days ago I wondered why we used custom oslo module
> instead of lockfile library [1]. AFAIK, it must be due to this bug [2]
> (please fix me, if I wrong).
>
> This library is available on github [3] and
Thanks a ton John! It finally worked!
@Daniel, no firewall update is required.
@Eric, At the same time, I had to update
/home/dstack/devstack/lib/nova_plugins/hypervisor-docker to include sudo
for all docker commands. I think that could be one change we would need in
docker and a documentation up
On Wed, Jan 15 2014, Ben Nemec wrote:
> The problem is that lockfile doesn't really solve our current problem,
> which is where to put the lock files. Fortunately, it sounds like Julien
> is working on changes to lockutils to remove the file based locking,
> which should solve the issues we're hav
Thanks Tim and Liz, comments in line.
2014/1/15 Tim Schnell
> On 1/15/14 9:01 AM, "Liz Blanchard" wrote:
>
>
> >
> >On Jan 9, 2014, at 4:41 AM, Jay Lau wrote:
> >
> >
> >My bad, the image cannot be viewed.
> >
> >
> >Upload again.
> >
> >
> >
> >Thanks,
> >
> >
> >Jay
> >
> >
> >
> >2014/1/9
So I upgraded some of my development hosts to Fedora 20
recently, and since then I’ve been hitting an issue where I
cannot start nova-compute at all. The environment I am running
this in is that the Fedora 20 hosts are running as VMs on a
Macbook Pro under VMware Fusion. The same setup works
fine w
On Jan 15, 2014, at 6:40 AM, Doug Hellmann wrote:
>
>
>
> On Wed, Jan 15, 2014 at 6:51 AM, Victor Sergeyev
> wrote:
> Hello All.
>
> As for lockutils - a few days ago I wondered why we used custom oslo module
> instead of lockfile library [1]. AFAIK, it must be due to this bug [2]
> (ple
Hi Guys
As Maru pointed out - NetworkBasicOps scenario has grown out of proportion and
is no longer "basic" ops.
So, I started breaking it down to smaller test cases that can fail
independently.
Those test cases share the same setup and tear-down code:
1. create network resources (and verify th
>
>
> @Eric, At the same time, I had to update
> /home/dstack/devstack/lib/nova_plugins/hypervisor-docker to include sudo
> for all docker commands. I think that could be one change we would need in
> docker and a documentation update for not using 127.0.0.1. I will create a
> bug and will submit a
Greeting,
In compute/manager.py, there is a periodic task named as
update_available_resource(), it will update resource for each compute
periodically.
@periodic_task.periodic_task
def update_available_resource(self, context):
"""See driver.get_available_resource()
Periodic p
On Wed, Jan 15, 2014 at 6:02 AM, Thierry Carrez wrote:
> Joe Gordon wrote:
> >> [1]
> >
> https://www.google.com/calendar/ical/[email protected]/public/basic.ics
> >
> > Is this calendar periodically pruned of dead meetings (for some
> > definition of dead)? If n
On Tue, Jan 14, 2014 at 2:22 PM, Dugger, Donald D wrote:
> All-
>
>
>
> I want to clear up some confusion I’m seeing in the reviews of these
> syncup patches. These patches merely bring recent changes from the nova
> tree over to the gantt tree. There is no attempt to actually change the
> cod
On 2014-01-15 07:05, Flavio Percoco wrote:
On 15/01/14 07:44 -0500, Doug Hellmann wrote:
[...]
I don't see a problem with doing that, but I'm not clear on
where we're
including the hash. In the file itself, in a separate file,
and/or in
the
commit message?
Okay I will give a try adding the stack user to docker group and adding
error message if it fails due to 127.0.0.1.
Also will file a bug report for the same.
Best Regards,
Swapnil
On Wed, Jan 15, 2014 at 9:53 PM, Eric Windisch wrote:
>
>> @Eric, At the same time, I had to update
>> /home/dsta
On Wed, Jan 15, 2014 at 11:09 AM, Vishvananda Ishaya
wrote:
>
> On Jan 15, 2014, at 6:40 AM, Doug Hellmann
> wrote:
>
>
>
>
> On Wed, Jan 15, 2014 at 6:51 AM, Victor Sergeyev
> wrote:
>
>> Hello All.
>>
>> As for lockutils - a few days ago I wondered why we used custom oslo
>> module instead of
Hi Eric
Small world dude. :-)
Have a nice day!
johnu
From: Eric Windisch [[email protected]]
Sent: Wednesday, January 15, 2014 7:33 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Openstack][Nova][Docker] Devstack
Looks like lbaas meeting is still alive:
from eavesdrop:
neutron_lbaas - 09-Jan-2014 14:01
neutron_lbaas_subteam_meeting - 05-Dec-2013 14:00
nuetron_lbaas - 28-Nov-2013 14:02
On Wed, Jan 15, 2014 at 8:24 PM, Joe Gordon wrote:
>
>
> On Wed, Jan 15, 2014 at 6:02 AM, Thierry Carrez wrote:
>
>> J
Very nice write up +1
A question, many modules are pulling in oslo.log as seen from the dependency
graph which itself then pulls in oslo.config. Is the plan to just have all
these modules use the regular python logging and have oslo.log be a
plugin/formatter/adapter to python logging?
Likely p
The current thought is that I will do the work to backport any change that are
made to the nova tree that overlap the gantt tree. I don't see this as an
impossible task. Yes it will get harder as we make specific changes to gantt
but, given that our first goal is to make gantt a drop in replac
Hi,
Ken'ichi Omichi submitted a change [1] in devstack to change the default
log level to 1 for libvirt. This results in continual spam to
/var/log/messages in my development system, even after exiting
devstack. The spam looks like:
"
Jan 14 08:13:49 bigiron libvirtd: 2014-01-14 15:13:49.33
It might help if we knew from operators whether they tended to use the
service config file or logging.conf to configure logging for their
installations. Maybe the service config file logging options are limited
enough that installations all use logging.conf.
It might make it a lot easier for devel
On 1/15/14 10:05 AM, "Jay Lau" wrote:
>Thanks Tim and Liz, comments in line.
>
>
>
>2014/1/15 Tim Schnell
>
>On 1/15/14 9:01 AM, "Liz Blanchard" wrote:
>
>
>>
>>On Jan 9, 2014, at 4:41 AM, Jay Lau wrote:
>>
>>
>>My bad, the image cannot be viewed.
>>
>>
>>Upload again.
>>
>>
>>
>>Thanks,
>>
>
Hi.
Implementing API on Pecan is a subthread of unification of openstack
components
activity.
In this context we have to do the job in any case.
I totally agree with cases Roman Prykhodchenko described.
If we swap versions now we'll have this part of work done. At that moment,
when
we'll need new
On 01/15/2014 11:56 AM, Steven Dake wrote:
Hi,
Ken'ichi Omichi submitted a change [1] in devstack to change the
default log level to 1 for libvirt. This results in continual spam to
/var/log/messages in my development system, even after exiting
devstack. The spam looks like:
"
Jan 14 08:13
+1 for your change. I've been hit by the very same issue today.
Simon
On 15/01/2014 17:56, Steven Dake wrote:
Hi,
Ken'ichi Omichi submitted a change [1] in devstack to change the default
log level to 1 for libvirt. This results in continual spam to
/var/log/messages in my development system,
On Wed, Jan 15, 2014 at 8:52 AM, Dugger, Donald D wrote:
> The current thought is that I will do the work to backport any change
> that are made to the nova tree that overlap the gantt tree. I don’t see
> this as an impossible task. Yes it will get harder as we make specific
> changes to gantt
Hi folks
Security group for OVS agent (ovs plugin or ML2) is being broken.
so we need vif_security port binding to fix this
(https://review.openstack.org/#/c/21946/)
We got discussed about the architecture for ML2 on ML2 weekly meetings, and
I wanna continue discussion in here.
Here is my propos
On Wed, Jan 15, 2014 at 05:28:07PM +, Daniel P. Berrange wrote:
> On Wed, Jan 15, 2014 at 09:56:58AM -0700, Steven Dake wrote:
>
> Agreed, it is complete insanity to set 'log_level=1' on *any* hosts.
> The level of debug info that generates is so enourmous that you'd
> never wanted to look at
On Wed, Jan 15, 2014 at 09:56:58AM -0700, Steven Dake wrote:
> Hi,
>
> Ken'ichi Omichi submitted a change [1] in devstack to change the
> default log level to 1 for libvirt. This results in continual spam
> to /var/log/messages in my development system, even after exiting
> devstack. The spam lo
On 2014-01-15 11:13, David Kranz wrote:
> On 01/15/2014 11:56 AM, Steven Dake wrote:
>
>> Hi,
>>
>> Ken'ichi Omichi submitted a change [1] in devstack to change the default log
>> level to 1 for libvirt. This results in continual spam to /var/log/messages
>> in my development system, even
On Wed, Jan 15, 2014 at 11:49 AM, Joshua Harlow wrote:
> Very nice write up +1
>
> A question, many modules are pulling in oslo.log as seen from the
> dependency graph which itself then pulls in oslo.config. Is the plan to
> just have all these modules use the regular python logging and have
> o
I've finally posted the notes we took at the icehouse summit for various
fixes needed to individual modules in Oslo [1].
It would be a great help if maintainers would take a quick look through the
notes and open bugs for the items in your module(s), but I will try to make
some time to do that next
- Original Message -
> From: "PAUL CARVER"
> To: [email protected]
> Sent: Wednesday, January 15, 2014 6:52:32 AM
> Subject: [openstack-dev] [Neutron] Partially Shared Networks
>
>
>
> The particular use case I have in mind concerns networks that could
> technically be cr
On Wed, Jan 15, 2014 at 5:28 AM, Frittoli, Andrea (Cloud Services) <
[email protected]> wrote:
> Hi all,
>
>
>
> I’ve been working on a patch to ensure that all tempest tests are able to
> handle rate limiting errors with automatic retries [0].
>
> API tests already implement retries, however scenar
On Wed, Jan 15, 2014 at 11:35 AM, Daniel P. Berrange wrote:
>
> I see that something close to this has already been added to devstack:
>
> https://review.openstack.org/#/c/65834/2/lib/nova
>
> which is the right way to tailor logging levels.
>
> So we should definitely revert https://review.opens
On 01/15/2014 10:28 AM, Daniel P. Berrange wrote:
On Wed, Jan 15, 2014 at 09:56:58AM -0700, Steven Dake wrote:
Hi,
Ken'ichi Omichi submitted a change [1] in devstack to change the
default log level to 1 for libvirt. This results in continual spam
to /var/log/messages in my development system,
On Wed, Jan 15, 2014 at 8:49 AM, Sergey Lukjanov wrote:
> Looks like lbaas meeting is still alive:
>
> from eavesdrop:
>
> neutron_lbaas - 09-Jan-2014 14:01
> neutron_lbaas_subteam_meeting - 05-Dec-2013 14:00
> nuetron_lbaas - 28-Nov-2013 14:02
>
Thanks for the correction, that leaves 3 possibly
Frittoli,
I don't think that this is a good idea. Because the main role of tempest is
to ensure that cloud works. So if it doesn't work we should change
something in deployment configuration or code to fix it. Not just hide with
monkey patches in tempest.
Probably you should try to implement ret
On 01/15/2014 10:13 AM, David Kranz wrote:
On 01/15/2014 11:56 AM, Steven Dake wrote:
Hi,
Ken'ichi Omichi submitted a change [1] in devstack to change the
default log level to 1 for libvirt. This results in continual spam
to /var/log/messages in my development system, even after exiting
dev
Cheers Guys
So what would you recommend Oleg. Yes its for linux system.
/Alan
From: Oleg Gelbukh [mailto:[email protected]]
Sent: January-15-14 10:30 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [ironic] Disk Eraser
On Wed, Jan 15, 2014 a
Hi,
When read Ceilometer install guide[1], the multi valued option
notification_driver is set to two drivers, My question is that is the first
one, which means nova.openstack.common.notifier.rpc_notifier, necessary?
what will happen if it is removed?
Note, it is not configured even in Nova instal
My thought was to try and get some parallel effort going, do the resync as a
continuing task as suffer a little ongoing pain versus a large amount of pain
at the end. Given that the steps for a resync are the same no matter when we
do it waiting until the end is acceptable.
>From a `just do it
On Wed, Jan 15, 2014 at 11:25 AM, Alan Kavanagh
wrote:
> Cheers Guys
>
>
>
> So what would you recommend Oleg. Yes its for linux system.
>
>
>
> /Alan
>
>
>
> From: Oleg Gelbukh [mailto:[email protected]]
> Sent: January-15-14 10:30 AM
> To: OpenStack Development Mailing List (not for usage qu
A number of folks have contacted me and stated that they couldn't get
the newly added cinder certification script to run. I looked into it
this morning, sdague pointed out that tempest/run_tests.sh was
modified a little while back and it turns out that was the source of
the problem.
I've logged a
On 01/15/2014 01:00 PM, Steven Dake wrote:
> On 01/15/2014 10:28 AM, Daniel P. Berrange wrote:
>> On Wed, Jan 15, 2014 at 09:56:58AM -0700, Steven Dake wrote:
>>> Hi,
>>>
>>> Ken'ichi Omichi submitted a change [1] in devstack to change the
>>> default log level to 1 for libvirt. This results in co
Excerpts from Jaromir Coufal's message of 2014-01-15 02:05:52 -0800:
> > 1) Check for an already deleted server before deleting any. This is
> > related to stack convergence:
> >
> > https://blueprints.launchpad.net/heat/+spec/stack-convergence
> >
> > This will allow users to just delete a server
Excerpts from Jiří Stránský's message of 2014-01-13 07:45:53 -0800:
> On 13.1.2014 11:43, Jaromir Coufal wrote:
> > On 2014/10/01 21:17, Jay Dobies wrote:
> >> Another question:
> >>
> >> - A Role (sounds like we're moving away from that so I'll call it
> >> Resource Category) can have multiple Nod
Here's the process I use to review a oslo-incubator merge... since I'm
mostly reviewing keystone I'm going to use that as the project.
1) Make sure keystone master is at the latest, and that oslo-incubator is
at the right level (the commit hash if they mentioned it or latest)
2) run update.py in o
Excerpts from Walls, Jeffrey Joel (Cloud OS R&D)'s message of 2014-01-15
07:04:48 -0800:
> > -Original Message-
> > From: James Slagle [mailto:[email protected]]
> > Sent: Wednesday, January 15, 2014 5:52 AM
> > To: OpenStack Development Mailing List (not for usage questions)
> > Subj
Hi,
Below are the set of steps we are using for Jenkins setup and would like
some clarifications reg some of the steps.
Under Jenkins/Configure
1. Source Code Management: to be git and point to the devstack URL
2. Build Triggers: Gerrit Event
3. Build/Execute Shell: Sequence of commands
I absolutely agree with that. Honestly, I don’t even understand why it can be
different (not compliant with regular grammar rules). Comments are supposed to
clarify things so they should be worded very clearly and read as normal English
sentences. Additionally it’s one of the small bricks that t
Greg,
Looks like I missed your last email in an email storm after NY holidays but now
was able to see it accidentally. So answering your question about Mistral
incubation your concern is valid. We’re currently working on moving Mistral
into incubation and we’ll keep you (and others) posted on t
1 - 100 of 172 matches
Mail list logo
