Well it's nice to fix, but I really don't know if we should be fixing it.
As discussed in one of the Ironic meetings before, we might need to define
what is our driver API or SDK or DDK or whatever we choose to call it .
Please see inline for my thoughts.
On Tue, Oct 6, 2015 at 5:54 AM, Devananda
On my top of mind for Mitaka:
*Introducing common Classifier Model [1]:*Currently, neutron service/s
(e.g. Service Function Chaining, QoS, Tap as a Service, FWaaS, Security
Group etc) which requires traffic classification defines their own
classifier model. This introduces redundancy. In order to
Hi all,
Has anyone done any performance tests on heat-api servers on any standard
setup so as to know how many stack requests it can handle before it can
stumble so that we can deploy scaling of heat-servers ??
Thanks
Eswar
_
Hi,
Following is the subteam report for Ironic. As usual, this is pulled
directly from the Ironic whiteboard[0] and formatted.
Bugs (dtantsur)
- (diff with Sep 28, no diff for inspector)
- Open: 137 (+2). 4 new (-5), 34 in progress (-2), 0 critical, 7 high
and 13 incomplete (+4)
Our team meeting is tomorrow at 14:00 UTC.
I made a couple changes to the agenda this week and added a new
sections called "Review Highlights" which I hope will help us discuss
and move forward some patches that look promising:
https://wiki.openstack.org/wiki/Meetings/TripleO#Review_Highlights
If
(Cross-posting to the operators list for feedback)
Thank you Ihar for starting this up. In the absence of any kind of
blog or other outlet of my own to disseminate this, let me share my
plans here...
Routed Networks:
My plans for Mitaka (and beyond) are around routed networks. During
Liberty,
Team,
In accordance with our consensus and the current date/time, I hereby welcome
Vilobh and Hua as new core reviewers, and have added them to the magnum-core
group. I will announce this addition at tomorrow’s team meeting at our new time
of 1600 UTC (no more alternating schedule, remember?).
tldr; the boot / deploy interface split we did broke an out of tree driver.
I've proposed a patch. We should get a fix into stable/liberty too.
Longer version...
I was rebasing my AMTTool driver [0] on top of master because the in-tree
one still does not work for me, only to discover that my driv
On 29 September 2015 at 08:28, Chris Hoge wrote:
> On Sep 29, 2015, at 8:04 AM, Erlon Cruz wrote:
>
>
> Hi Cris,
>
> There are some questions that came to my mind.
>
> Cinder has near zero tolerance to backends that does not have a CI
> running. So, can one assume that all drivers in Cinder will
Thanks, I'm triaging this now.
On 06/10/15 11:41, Mingyu Li wrote:
Hi all,
There seems a bug in stable/liberty branch.
https://bugs.launchpad.net/heat/+bug/1503060
In an environment installed with Devstack and stable/liberty branch,
stack creation fails when I use some templates that worked
On 06/10/15 06:23, Ben Nemec wrote:
On 10/05/2015 12:12 PM, Jeremy Stanley wrote:
On 2015-10-05 12:00:31 -0500 (-0500), Ben Nemec wrote:
[...]
Note that it's best to do this once the change is ready to be
approved. If you do it earlier and the committer pushes a new
patch set without fixing the
Hi all,
There seems a bug in stable/liberty branch.
https://bugs.launchpad.net/heat/+bug/1503060
In an environment installed with Devstack and stable/liberty branch, stack
creation fails when I use some templates that worked well with stable/kilo,
such as the following:
heat_template_version: 2
On 2015-10-05 22:14:20 + (+), Jeremy Stanley wrote:
> On 2015-10-05 16:56:50 -0400 (-0400), Ronald Bradford wrote:
> [...]
> > - Anything else relevant regarding code coverage being more consistent
> > for OpenStack.
>
> I do have https://review.openstack.org/171331 to get PBR to stop
> st
On 2015-10-05 16:56:50 -0400 (-0400), Ronald Bradford wrote:
[...]
> - Anything else relevant regarding code coverage being more consistent
> for OpenStack.
I do have https://review.openstack.org/171331 to get PBR to stop
stepping on the package name if set in .coveragerc, though it's
still WIP du
[ Was: Re: [openstack-dev] OpenStack-dev Digest, Vol 41, Issue 49]
Santosh Parihar,
This implies that the nodes are (in order of most to least likely):
a) currently offline
b) un-accessible from the fuel master node
c) the mcollective agent is not running on them
d) rabbitmq on the fuel node (rab
OSTF was designed to be a post-deployment test framework. We may introduce
pre- and post-deployment tests in Fuel, but from an implementation point of
view the "pre-" should be done by Nailgun/Astute and the "post-" by OSTF. I
don't think we should mix both in OSTF.
On Tue, Sep 29, 2015 at 10:02 A
Excerpts from Ronald Bradford's message of 2015-10-05 16:56:50 -0400:
> As part of reviewing the code coverage on various projects I have found
> that a number had failing coverage jobs when not configured correctly (many
> also work just fine). Starting initially in various Oslo projects my goal
As part of reviewing the code coverage on various projects I have found
that a number had failing coverage jobs when not configured correctly (many
also work just fine). Starting initially in various Oslo projects my goal
has been to just ensure coverage is defined, runs without errors and is
gene
>
>
>>
> Mirantis does control neither Rabbitmq or Galera. Mirantis cannot assure
> their quality as well.
>
Correct, and rabbitmq was always the pain in the back, preventing any *real
*enterprise usage of openstack where reliability does matter.
> > 2) it has terrible UX
>>
>
> It looks like pe
Note: I sent a message to Thierry and Doug for help with the specifics of
running the release and after Theirry’s response it seemed we should include
the mailing list.
>Tripp, Travis S wrote:
>>Theirry and Doug,
>>We are down to a single patch that needs one more +2 and then we believe
>>we’ll
A kind reminder for tomorrow's meeting.
Please add agenda items to the meeting here [1].
See you all tomorrow!
Armando
[1] https://wiki.openstack.org/wiki/Network/Meetings
__
OpenStack Development Mailing List (not for usag
Hi neutrinos,
One of the areas I would like to work on during the Mitaka cycle is
'consistency' [1].
We've grown quite a bit during the last cycle and we need to make sure we
are on the same page when it comes to code quality and reviews, and at the
same time speeding up review velocity without c
On Mon, Oct 5, 2015 at 2:15 PM, Korzeniewski, Artur <
artur.korzeniew...@intel.com> wrote:
> Hi Code Reviewers,
>
> I would like to ask if DVR-HA patches can be merged into Liberty release:
>
> https://bugs.launchpad.net/neutron/+bug/1365473
>
> https://review.openstack.org/#/c/196893
>
> https://
Hello everyone,
Due to release-critical issues spotted in Trove and Barbican during RC1
testing, new release candidates were created for Liberty. The list of
RC2 fixes, as well as RC2 tarballs are available at:
https://launchpad.net/trove/liberty/liberty-rc2
https://launchpad.net/barbican/liberty
Cool. That works.
On Mon, Oct 5, 2015 at 9:05 AM, Russell Bryant wrote:
> On 10/05/2015 04:28 PM, Murali R wrote:
> > Yes. So we can define multiple logical switches per network and ovn
> > keeps vlan maps that ovs agent used to maintain and do the tunneling. My
> > confusion was from lport-add
Hi Code Reviewers,
I would like to ask if DVR-HA patches can be merged into Liberty release:
https://bugs.launchpad.net/neutron/+bug/1365473
https://review.openstack.org/#/c/196893
https://review.openstack.org/#/c/143169
The proper patches has been implemented, the reviews has been addressed, t
Hi everyone,
The OpenStack Infrastructure (Infra) team is having our next weekly
meeting on Tuesday October 6th, at 19:00 UTC in #openstack-meeting
Meeting agenda available here:
https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting (anyone is
welcome to to add agenda items)
Everyone interes
On 6 October 2015 at 03:34, Roman Prykhodchenko wrote:
> Disclaimer:
> I didn’t want to fire up this war but it silently hit one of my patches so
> now I think it’s better to spread it to a wide audience.
>
>
> When I was dealing with one of the regular dependency hell in Fuel Client I
> noticed
On 10/05/2015 12:12 PM, Jeremy Stanley wrote:
> On 2015-10-05 12:00:31 -0500 (-0500), Ben Nemec wrote:
> [...]
>> Note that it's best to do this once the change is ready to be
>> approved. If you do it earlier and the committer pushes a new
>> patch set without fixing the commit message, it will re
On 2015-10-05 12:00:31 -0500 (-0500), Ben Nemec wrote:
[...]
> Note that it's best to do this once the change is ready to be
> approved. If you do it earlier and the committer pushes a new
> patch set without fixing the commit message, it will revert the
> fix made through the web interface.
Well,
On 10/01/2015 02:56 AM, Ghe Rivero wrote:
> If anyone disagrees with the commit format, please, go ahead and fix it (It's
> really easy using the gerrit web) For such cosmetic changes (and others
> similars), we should not wait for the author to do it. Sometimes, for a stupid
> comma, and with all
Excerpts from Dean Troyer's message of 2015-10-05 11:18:55 -0500:
> On Mon, Oct 5, 2015 at 11:03 AM, Doug Hellmann
> wrote:
>
> > Devstack should also look at using the shell output formatter,
> > especially for show commands. Combining that formatter with eval means
> > no parsing in a lot of ca
On Mon, Oct 5, 2015 at 11:03 AM, Doug Hellmann
wrote:
> Devstack should also look at using the shell output formatter,
> especially for show commands. Combining that formatter with eval means
> no parsing in a lot of cases.
>
It may in places, but it turns out the 'value' formatter is most usefu
On 10/05/2015 04:28 PM, Murali R wrote:
> Yes. So we can define multiple logical switches per network and ovn
> keeps vlan maps that ovs agent used to maintain and do the tunneling. My
> confusion was from lport-add command that did not have host info, so if
> there is no neutron, the cms has to ma
Excerpts from Sean Dague's message of 2015-10-05 06:57:06 -0400:
> On 10/05/2015 12:16 AM, Steve Martinelli wrote:
> > I loved reading this email as much as zigo loves csv output, great
> > feedback is an amazing motivator!
> >
> > And don't worry, the csv output was never going away :)
> >
> > s
Chuck Short wrote:
> I would like to freeze the branches on Wednesday and get a release out
> early next week. Are we okay with that?
Next week is Liberty release week so that might be confusing...
But if it's the only option, as long as it's *early* next week, I guess
that won't hurt.
--
Thierr
Hello everyone,
In order to include last-minute translations updates, a new liberty
release candidate was created for Zaqar. RC2 tarballs are available at:
https://launchpad.net/zaqar/liberty/liberty-rc2
Unless new release-critical issues are found that warrant a last-minute
release candidate re
Yes. So we can define multiple logical switches per network and ovn keeps
vlan maps that ovs agent used to maintain and do the tunneling. My
confusion was from lport-add command that did not have host info, so if
there is no neutron, the cms has to maintain the host to lport association
and we can'
On 5 October 2015 at 03:14, Ihar Hrachyshka wrote:
> > On 02 Oct 2015, at 02:37, Armando M. wrote:
> >
> > Hi neutrinos,
> >
> > Whilst we go down the path of revising the way we manage/process bugs in
> Neutron, and transition to the proposed model [1], I was wondering if I can
> solicit some v
Thierry Carrez wrote:
> [...] Here is the resulting proposed room/time layout result:
>
> http://tinyurl.com/mitaka-design-summit
OK, I just pushed this track layout to the official Design Summit
schedule at:
https://mitakadesignsummit.sched.org/
> [...]
> I'll push this proposed layout to Ched
Hi together,
I think it would be very helpful if you all could update your launchpad
profile with your timezone information. This makes it more easy to
figure out the timeframe when a person can be reached in theory.
To update your account, use this link
https://launchpad.net/people/+me/+editlo
Disclaimer:
I didn’t want to fire up this war but it silently hit one of my patches so now
I think it’s better to spread it to a wide audience.
When I was dealing with one of the regular dependency hell in Fuel Client I
noticed, that stuff which is not in global requirements may make the mentio
Hi,
On Mon, Oct 5, 2015 at 3:03 PM, Alex Schultz wrote:
> On Mon, Oct 5, 2015 at 5:56 AM, Eugene Nikanorov
> wrote:
> > Ok,
> >
> > Project-wise:
> > 1) Pacemaker is not under our company's control, we can't assure its
> quality
>
Mirantis does control neither Rabbitmq or Galera. Mirantis can
Hi team,
Last week I had sent out an email proposing changes to our weekly IRC meeting
time
(see below for reference). There was no objection to this proposal.
The patch that makes this change official is now merged.
https://review.openstack.org/#/c/228441/
Starting tomorrow (October 6), our we
> On 05 Oct 2015, at 15:32, Gary Kotton wrote:
>
>
>
> On 10/5/15, 3:21 AM, "Ihar Hrachyshka" wrote:
>
>>> On 04 Oct 2015, at 19:21, Gary Kotton wrote:
>>>
>>> Sorry, it is not a result of the AZ support (humble apologies)
>>>
>>> It is a result of https://review.openstack.org/#/c/226362/
From: Akihiro MOTOKI mailto:amot...@gmail.com>>
Reply-To: OpenStack List
mailto:openstack-dev@lists.openstack.org>>
Date: Monday, October 5, 2015 at 3:48 PM
To: OpenStack List
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Neutron] AZ Support
Hi,
2015-10-05 15:54 GMT
On 10/5/15, 3:21 AM, "Ihar Hrachyshka" wrote:
>> On 04 Oct 2015, at 19:21, Gary Kotton wrote:
>>
>> Sorry, it is not a result of the AZ support (humble apologies)
>>
>> It is a result of https://review.openstack.org/#/c/226362/
>
>So you use DHCP agent with non-ml2 plugin, and it broke you.
Hi,
Most of the people involved in the project won't be able to attend
today's meeting. Meeting is canceled.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.o
On Mon, Oct 5, 2015 at 5:56 AM, Eugene Nikanorov
wrote:
> Ok,
>
> Project-wise:
> 1) Pacemaker is not under our company's control, we can't assure its quality
> 2) it has terrible UX
> 3) it is not reliable
>
I disagree with #1 as I do not agree that should be a criteria for an
open-source projec
Hi,
This is a reminder that we’ll hold a team meeting today at #openstack-meeting
at 16.00 UTC.
Agenda:
Review action items
Current status (progress, issues, roadblocks, further plans)
UI progress
Official Liberty Release health
Bugfixing progress
Documentation progress
Open discussion
Feel fre
Hi,
2015-10-05 15:54 GMT+09:00 Gary Kotton :
> Hi,
> Yes, you are correct. That patch is the culprit (my bad and once again
> humble apologies)
>
> Regarding the AZ support I think that we need to do the following:
>
>1. Have this in a separate topic until it is complete. I have a number
>
Hello!
Here's an initial agenda for our weekly meeting, tomorrow at 1500 UTC
in #openstack-meeting-4:
https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20151006
Feel free to add any additional items you'd like to discuss.
If our schedule allows it, we'll make bug triage during the
Hi,
I would like to freeze the branches on Wednesday and get a release out
early next week. Are we okay with that?
Thanks
chuck
On Wed, Sep 23, 2015 at 8:47 PM, Chuck Short
wrote:
> Hi,
>
> We would like to do a stable/kilo branch release, next Thursday. In order
> to do that I would like to f
On 10/05/2015 12:16 AM, Steve Martinelli wrote:
> I loved reading this email as much as zigo loves csv output, great
> feedback is an amazing motivator!
>
> And don't worry, the csv output was never going away :)
>
> stevemar
It might be nice to change some of the devstack usage into that. It
wo
OK, I propose to move further discussions of the topic to this particular
changeset review.
Pavel
On Mon, Oct 5, 2015 at 1:25 PM, Daniel P. Berrange
wrote:
> On Mon, Oct 05, 2015 at 01:10:45PM +0300, Pavel Boldin wrote:
> > Daniel,
> >
> > It is done already in the proposed patch.
> >
> > But t
Ok,
Project-wise:
1) Pacemaker is not under our company's control, we can't assure its quality
2) it has terrible UX
3) it is not reliable
(3) is not evaluation of the project itself, but just a logical consequence
of (1) and (2).
As a part of escalation team I can say that it has cost our team t
On Mon, Oct 5, 2015 at 12:22 PM, Eugene Nikanorov
wrote:
> No pacemaker for os services, please.
> We'll be moving out neutron agents from pacemaker control in 8.0, other os
> services don't need it too.
>
could you please provide your arguments.
/sv
___
On Mon, Oct 05, 2015 at 01:10:45PM +0300, Pavel Boldin wrote:
> Daniel,
>
> It is done already in the proposed patch.
>
> But this one is about Wily having libvirt 1.2.16 and libvirt-python 1.2.15.
Assuming you are refering to this patch:
https://review.openstack.org/#/c/227278/3/nova/virt/libv
On 01/10/15 20:34, Dan Prince wrote:
> On Wed, 2015-09-30 at 21:05 +0100, Steven Hardy wrote:
>> Hi all,
>>
>> So I wanted to start some discussion on $subject, because atm we have
>> a
>> couple of patches adding support for new services (which is great!):
>>
>> Manila: https://review.openstack.or
> On 04 Oct 2015, at 19:21, Gary Kotton wrote:
>
> Sorry, it is not a result of the AZ support (humble apologies)
>
> It is a result of https://review.openstack.org/#/c/226362/
So you use DHCP agent with non-ml2 plugin, and it broke you. Do you think it’s
ok for you to change the RPC topic to
Daniel,
It is done already in the proposed patch.
But this one is about Wily having libvirt 1.2.16 and libvirt-python 1.2.15.
Pavel
On Mon, Oct 5, 2015 at 11:25 AM, Daniel P. Berrange
wrote:
> On Fri, Oct 02, 2015 at 04:38:30PM -0400, Mathieu Gagné wrote:
> > On 2015-10-02 4:18 PM, Pavel Bold
Very nice thread Ihar!
Here are my plans:
1. Get the last patches of the blueprint restructure-l2-agent merged
and keep working on improving the agent. Some code refactor is
definitely needed and I'd like to add multiple workers.
2. Introducing oslo versioned objects
3. Make it easier to get s
> On 02 Oct 2015, at 02:37, Armando M. wrote:
>
> Hi neutrinos,
>
> Whilst we go down the path of revising the way we manage/process bugs in
> Neutron, and transition to the proposed model [1], I was wondering if I can
> solicit some volunteers to screen the bugs outlined in [2]. It's only 24
Hi,
I have some plans in Mitaka cycle.
1. AZ support[1]
- I proposed AZ support in Liberty but the millstone is Mitaka now. The spec
has been merged in Mitaka.
I keep to propose the patches on Gerrit.
2. LinuxbrideDVR
- I'm trying to create concrete implementation and then I achieve it near
No pacemaker for os services, please.
We'll be moving out neutron agents from pacemaker control in 8.0, other os
services don't need it too.
E.
5 окт. 2015 г. 12:01 пользователь "Sergii Golovatiuk" <
sgolovat...@mirantis.com> написал:
> Good morning gentlemen!
>
> Alex raised very good question.
Good morning gentlemen!
Alex raised very good question. Thank you very much! We have 3 init systems
right now. Some services use SystemV, some services use upstart, some
services are under pacemaker. Personally, I would like to have pacemaker as
pid 1 to replace init [1]. However, I would like to
On Fri, Oct 02, 2015 at 04:38:30PM -0400, Mathieu Gagné wrote:
> On 2015-10-02 4:18 PM, Pavel Boldin wrote:
> >
> > You have to pass device names from /dev/, e.g., if a VM has
> > ephemeral disk
> > attached at /dev/vdb you need to pass in 'vdb'. Format expected by
> > migrate_disk
Hi Gary,
Thank you for your suggestion.
In Liberty cycle[1], I have discussed about these points with neutron folks and
network operators.
> On 2015/10/05, at 15:54, Gary Kotton wrote:
>
> Hi,
> Yes, you are correct. That patch is the culprit (my bad and once again humble
> apologies)
>
> R
Hi all,
I have permission-related errors when creating instances.
In Kilo,
since my local disk is small, newly attaching a new disk, /data1 as
following.
root@cn2:/var/lib/nova# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda5 23G 1.7G 20G 8% /
...
/dev/mapper/vg_data-lv_data1 356G 7
69 matches
Mail list logo
