Re: [openstack-dev] TC Candidacy

On Mon, Oct 3, 2016 at 11:33 AM, Clay Gerrard wrote: > > > On Thu, Sep 29, 2016 at 8:34 PM, John Griffith > wrote: > >> >> >> I think what's more important and critical is the future and where >> OpenStack is going over the course of the next

[openstack-dev] [nova] Future of turbo-hipster CI

Howdy, Quick bit of background. Turbo-hipster is a 3rd party CI system that runs nova's database migrations against real datasets to try and catch real-world problems. When it was initially written the state of migrations in nova would cause a lot of pain for deployers (such as very long

Re: [openstack-dev] [tc] open question to the candidates

On Mon, Oct 3, 2016 at 9:30 AM, gordon chung wrote: > hi, > > as there are many candidates this TC election, i figured i'd ask a > question to better understand the candidates from the usual sales pitch > in self-nominations. hopefully, this will give some insights into the >

Re: [openstack-dev] TC Candidacy

On 2016-10-03 12:23:47 -0700 (-0700), Clay Gerrard wrote: > This was a riveting soapbox missive - and I agree with what you said - > particularly about the focus on breaking down the barriers to building out > and supporting the OpenStack contributor base. Thanks! Rather than talk about myself or

Re: [openstack-dev] [all][elections][TC] TC candidacy

On Mon, Oct 03, 2016 at 10:53:30AM -0700, John Dickinson wrote: > > > On 27 Sep 2016, at 9:21, Sean McGinnis wrote: > > > I would like to announce my candidacy for a position on the Technical > > Committee. > > > > > Sean, > > Are there some specific areas of complexity that you would like to

Re: [openstack-dev] TC candidacy

On Mon, Oct 3, 2016 at 5:01 PM, Emilien Macchi wrote: > On Mon, Oct 3, 2016 at 2:50 PM, Clay Gerrard wrote: >> >> >> On Tue, Sep 27, 2016 at 2:52 PM, Emilien Macchi wrote: >>> >>> >>> - Make sure it works outside Devstack. >>> >>>

[openstack-dev] [puppet] useful logstash queries

I was looking for a quick way to find Puppet deprecations that we did in Newton and could clean-up in Ocata. Also I was searching for OpenStack deprecations. I found useful to create an etherpad with some logstash queries: https://etherpad.openstack.org/p/puppet-openstack-ci-logstash-queries

Re: [openstack-dev] [tc] open question to the candidates

On 2016-10-03 15:30:56 + (+), gordon chung wrote: [...] > the TC has historically been a reactive council that lets others ask for > change and acts as the final approver. do you believe the TC should be a > proactive committee that initiates change and if yes, to what scope? I view the

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

On Oct 3, 2016 14:15, "Edward Leafe" wrote: > > On Oct 3, 2016, at 12:18 PM, Clay Gerrard wrote: > > > >> After the nominations close, the election officials will assign each candidate a non-identifying label, such as a random number, and those officials

Re: [openstack-dev] FYI - gate completely borked on master and newton dsvm/grenade jobs

On Mon, Oct 03, 2016 at 07:19:46PM +, Jeremy Stanley wrote: > On 2016-10-03 16:11:25 + (+), Jeremy Stanley wrote: > [...] > > I think we can bring this thread to a close now. Upstream deleted > > the broken wheel from PyPI a little over an hour ago, and within > > about 5 minutes it

Re: [openstack-dev] migrate_flavor_data doesn't flavor migrate meta data of VMs spawned during upgrade.

Hi, I did some investigation last week, why this was happening before I file the bug. Here are my observations and I would like to work on it. Any guidance is appreciated. Upgrade procedure: In my setup I have openstack controller on one node, neutron on another node and rest of the nodes are

Re: [openstack-dev] [tc] open question to the candidates

On Mon, Oct 3, 2016, at 08:30 AM, gordon chung wrote: > the TC has historically been a reactive council that lets others ask for > change and acts as the final approver. do you believe the TC should be a > proactive committee that initiates change and if yes, to what scope? > more generally,

Re: [openstack-dev] [all][elections] Voting for the TC Election is now open

On Tue, Oct 04, 2016 at 09:32:54AM +1100, Tony Breeds wrote: > NOTE: The election officals have been contacted by a number of people stating > that they have not recieved thier ballot. In addition the email to > openstack-dev announcing the opening of the elction did not arrive. As such > the

Re: [openstack-dev] [tc] open question to the candidates

Excerpts from John Dickinson's message of 2016-10-03 14:26:00 -0700: > > On 3 Oct 2016, at 12:31, Doug Hellmann wrote: > > > > I think that's the balance we want to > > have: listen to input, collect information, then clearly set the > > direction without over-prescribing the implementation. > >

[openstack-dev] [all][elections] Voting for the TC Election is now open

NOTE: The election officals have been contacted by a number of people stating that they have not recieved thier ballot. In addition the email to openstack-dev announcing the opening of the elction did not arrive. As such the election officials are performing the following actions: 1. Extending

Re: [openstack-dev] [tc] open question to the candidates

On Mon, 3 Oct 2016, gordon chung wrote: the TC has historically been a reactive council that lets others ask for change and acts as the final approver. do you believe the TC should be a proactive committee that initiates change and if yes, to what scope? more generally, what are some specific

Re: [openstack-dev] TC candidacy

On Mon, 3 Oct 2016, Clay Gerrard wrote: I just re-read your announcement - and I couldn't be happier you're running :D a) Glad to hear it. b) It's a shame these email threads didn't start last week. I suspect many of the people reading have already voted. I think the conversations are still

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

On 2016-10-03 16:15:01 -0500 (-0500), Edward Leafe wrote: [...] > So I think that there is evidence that unless you are already > well-known, most people aren't going to take the time to dig > deeper. Maybe anonymous campaigns aren't the answer, but they > certainly would help in this regard.

Re: [openstack-dev] [Nova] Live migration sub-team lead

On 10/3/2016 12:31 PM, Timofei Durakov wrote: Paul, thanks for leading live migration sub-team. A lot of work were done in that area for last year! Best, Timofey On Mon, Oct 3, 2016 at 7:22 PM, Murray, Paul (HP Cloud) > wrote: Hi All, I

Re: [openstack-dev] [tc] open question to the candidates

On 3 Oct 2016, at 12:31, Doug Hellmann wrote: > > I think that's the balance we want to > have: listen to input, collect information, then clearly set the > direction without over-prescribing the implementation. In light of this statement, would you reevaluate previous decisions you've made

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

On Oct 3, 2016, at 1:39 PM, Clint Byrum wrote: > > Of course, I read the essays of those who I don't know more carefully, and > I often go searching through my ML archives to see if we've interacted on > threads in the past. Still, I'm very unlikely to rank somebody higher than

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

On Oct 3, 2016, at 12:18 PM, Clay Gerrard wrote: > >> After the nominations close, the election officials will assign each >> candidate a non-identifying label, such as a random number, and those >> officials will be the only ones who know which candidate is associated

[openstack-dev] [Mentoring] Call for Mentors for Barcelona events

Hello, We have two (2) great mentoring opportunities coming up for the Barcelona summit. These are a fairly short time commitment, so please consider taking a few hours to help out people new to the community. Upstream University - Sunday October 23rd, 1:00-5:00PM & Monday, October 24th,

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

On Oct 3, 2016, at 12:51 PM, Doug Hellmann wrote: > When I vote, I consider the positions a candidate takes, the ideas > they propose, and -- equally importantly -- their track record of > actually getting things done. Hiding the candidate's identity makes > it impossible

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

On 03/10/2016 1:18 PM, Clay Gerrard wrote: > I think a more common problem is when people vote for a *name* they > recognize without really knowing that person or what they're about. Or > perhaps just as bad - *not* voting because they realize they have on > context to consider these candidates

Re: [openstack-dev] TC candidacy

On Mon, Oct 3, 2016 at 2:50 PM, Clay Gerrard wrote: > > > On Tue, Sep 27, 2016 at 2:52 PM, Emilien Macchi wrote: >> >> >> - Make sure it works outside Devstack. >> >> There is a huge gap between what is tested by Devstack gate and what >> operators >>

Re: [openstack-dev] [oslo] Adding gdavoian to oslo-core

+1 for Gevorg! On Mon, Oct 3, 2016 at 2:02 PM, Davanum Srinivas wrote: > +1 from me! > > On Mon, Oct 3, 2016 at 1:40 PM, Joshua Harlow wrote: >> Greetings all stackers, >> >> I propose that we add Gevorg Davoian[1] to the oslo-core[2] team. >> >> Gevorg

Re: [openstack-dev] [oslo] Adding ozamiatin to oslo-core

+1 for sure. On Mon, Oct 3, 2016 at 1:42 PM, Joshua Harlow wrote: > Greetings all stackers, > > I propose that we add Oleksii Zamiatin[1] to the oslo-core[2] team. > > Oleksii has been actively contributing to oslo for a while now, both in > helping make oslo better via

Re: [openstack-dev] [tc] open question to the candidates

On Mon, Oct 3, 2016 at 11:30 AM, gordon chung wrote: > hi, > > as there are many candidates this TC election, i figured i'd ask a > question to better understand the candidates from the usual sales pitch > in self-nominations. hopefully, this will give some insights into the >

Re: [openstack-dev] [tc] open question to the candidates

Excerpts from gordon chung's message of 2016-10-03 15:30:56 +: > hi, > > as there are many candidates this TC election, i figured i'd ask a > question to better understand the candidates from the usual sales pitch > in self-nominations. hopefully, this will give some insights into the >

Re: [openstack-dev] TC candidacy

On Mon, Oct 3, 2016 at 2:50 PM, Clay Gerrard wrote: > Do you think this is an important topic for OpenStack right now? I'd be > really interested to hear any *new* insights from the previous PTL of *one* > of OpenStack's installation automation projects? What could or

Re: [openstack-dev] TC Candidacy

This was a riveting soapbox missive - and I agree with what you said - particularly about the focus on breaking down the barriers to building out and supporting the OpenStack contributor base. But I don't have a good sense for how you want to apply that focus in action on the TC? I went back and

Re: [openstack-dev] FYI - gate completely borked on master and newton dsvm/grenade jobs

Thanks for the prompt follow up Jeremy! -- Dims On Mon, Oct 3, 2016 at 3:19 PM, Jeremy Stanley wrote: > On 2016-10-03 16:11:25 + (+), Jeremy Stanley wrote: > [...] >> I think we can bring this thread to a close now. Upstream deleted >> the broken wheel from PyPI a

Re: [openstack-dev] FYI - gate completely borked on master and newton dsvm/grenade jobs

On 2016-10-03 16:11:25 + (+), Jeremy Stanley wrote: [...] > I think we can bring this thread to a close now. Upstream deleted > the broken wheel from PyPI a little over an hour ago, and within > about 5 minutes it disappeared from our CI system mirrors as well > (PyPI deletions propagate

[openstack-dev] [ironic] weekly subteam report

Hi, Here is this week's subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) === - Stats (diff between 26 Sep 2016 and 03 Oct 2016) - Ironic: 205 bugs (+10) + 212 wishlist items (-4). 6 new (+6), 169 in progress

Re: [openstack-dev] TC candidacy

On Tue, Sep 27, 2016 at 2:52 PM, Emilien Macchi wrote: > > - Make sure it works outside Devstack. > > There is a huge gap between what is tested by Devstack gate and what > operators > deploy on the field. This gap tends to stretch the feedback loop between > developers and

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

Excerpts from Edward Leafe's message of 2016-10-03 11:46:41 -0500: > So the period of self-nominations for the Technical Committee seats has > ended, and the voting has begun. I've been a very close observer of this > process for several cycles, and I have some ideas I'd like to share. Full >

[openstack-dev] [nova][bugs] Nova Bugs Team Meeting this Tuesday at 1800 UTC

The next Nova Bugs Team meeting will be Tuesday, October 3 at 1800 UTC in #openstack-meeting-4 http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160920T18 Feel free to add to the meeting agenda: https://wiki.openstack.org/wiki/Meetings/Nova/BugsTeam -- Augustina Ragwitz Señora

Re: [openstack-dev] [tc] open question to the candidates

gordon chung wrote: hi, as there are many candidates this TC election, i figured i'd ask a question to better understand the candidates from the usual sales pitch in self-nominations. hopefully, this will give some insights into the candidates for those who haven't voted yet. obviously, the

Re: [openstack-dev] [oslo] Adding gdavoian to oslo-core

+1 from me! On Mon, Oct 3, 2016 at 1:40 PM, Joshua Harlow wrote: > Greetings all stackers, > > I propose that we add Gevorg Davoian[1] to the oslo-core[2] team. > > Gevorg has been actively contributing to oslo for a while now, both in > helping make oslo better via code

Re: [openstack-dev] [oslo] Adding ozamiatin to oslo-core

+1 from me!. On Mon, Oct 3, 2016 at 1:42 PM, Joshua Harlow wrote: > Greetings all stackers, > > I propose that we add Oleksii Zamiatin[1] to the oslo-core[2] team. > > Oleksii has been actively contributing to oslo for a while now, both in > helping make oslo better via

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

Excerpts from Clay Gerrard's message of 2016-10-03 10:18:43 -0700: > On Mon, Oct 3, 2016 at 9:46 AM, Edward Leafe wrote: > > > After the nominations close, the election officials will assign each > > candidate a non-identifying label, such as a random number, and those > >

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

Excerpts from Hayes, Graham's message of 2016-10-03 17:35:44 +: > On 03/10/2016 17:49, Edward Leafe wrote: > > So the period of self-nominations for the Technical Committee seats has > > ended, and the voting has begun. I've been a very close observer of this > > process for several cycles,

Re: [openstack-dev] [all][elections][TC] TC candidacy

On 27 Sep 2016, at 9:21, Sean McGinnis wrote: > I would like to announce my candidacy for a position on the Technical > Committee. > > I work for Dell EMC with over a decade (quite a bit over, but I don't want to > think about that) in storage and software development. I have been involved in >

Re: [openstack-dev] TC candidacy

I just re-read your announcement - and I couldn't be happier you're running :D I was so surprised at the fallout from your suggestion that the TC should actively engage in more broadcasting of important topics [1] to bring in more voices from the community early!? Links to IRC logs and Gerrit

[openstack-dev] [oslo] Adding ozamiatin to oslo-core

Greetings all stackers, I propose that we add Oleksii Zamiatin[1] to the oslo-core[2] team. Oleksii has been actively contributing to oslo for a while now, both in helping make oslo better via code contribution(s) and by helping with the review load when he can. He has provided quality reviews

[openstack-dev] [oslo] Adding gdavoian to oslo-core

Greetings all stackers, I propose that we add Gevorg Davoian[1] to the oslo-core[2] team. Gevorg has been actively contributing to oslo for a while now, both in helping make oslo better via code contribution(s) and by helping with the review load when he can. He has provided quality reviews

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

On 03/10/2016 17:49, Edward Leafe wrote: > So the period of self-nominations for the Technical Committee seats has > ended, and the voting has begun. I've been a very close observer of this > process for several cycles, and I have some ideas I'd like to share. Full > disclosure: I am a current

Re: [openstack-dev] TC Candidacy

On Thu, Sep 29, 2016 at 8:34 PM, John Griffith wrote: > > > I think what's more important and critical is the future and where > OpenStack is going over the course of the next few years. > I think this is a really important topic right now! Do you see any dangerous

Re: [openstack-dev] [Nova] Live migration sub-team lead

Paul, thanks for leading live migration sub-team. A lot of work were done in that area for last year! Best, Timofey On Mon, Oct 3, 2016 at 7:22 PM, Murray, Paul (HP Cloud) wrote: > Hi All, > > I have had the pleasure of chairing the live migration sub-team for the > last

Re: [openstack-dev] [elections][tc]Thoughts on the TC election process

On Mon, Oct 3, 2016 at 9:46 AM, Edward Leafe wrote: > After the nominations close, the election officials will assign each > candidate a non-identifying label, such as a random number, and those > officials will be the only ones who know which candidate is associated with > which

[openstack-dev] email filter for starred changes in Gerrit?

Hi, Is there a way to identify an email notification from Gerrit that corresponds to a change you have starred? I'm trying to write an email filter to give these emails a special tag but I'm not seeing an easy way to do this. Thanks, Kevin Benton

[openstack-dev] [elections][tc]Thoughts on the TC election process

So the period of self-nominations for the Technical Committee seats has ended, and the voting has begun. I've been a very close observer of this process for several cycles, and I have some ideas I'd like to share. Full disclosure: I am a current candidate for the TC, and have been a candidate

Re: [openstack-dev] [tc] open question to the candidates

> -Original Message- > From: gordon chung [mailto:g...@live.ca] > Sent: Monday, October 03, 2016 11:31 AM > To: openstack-dev@lists.openstack.org > Subject: [openstack-dev] [tc] open question to the candidates > > hi, > > as there are many candidates this TC election, i figured i'd ask

Re: [openstack-dev] [neutron] bug deputy report

3. https://bugs.launchpad.net/neutron/+bug/1628044 - bgp listener not > listening on mitaka. Someone should validate the bug in latest code. >>> Ryu team got to check this issue... Neutron is not responsible for creating BGP peer... On Oct 3, 2016 8:26 PM, "Assaf Muller" wrote:

Re: [openstack-dev] [tc] open question to the candidates

On Mon, Oct 03, 2016 at 03:30:56PM +, gordon chung wrote: > > > the TC has historically been a reactive council that lets others ask for > change and acts as the final approver. do you believe the TC should be a > proactive committee that initiates change and if yes, to what scope? > more

[openstack-dev] [Nova] Live migration sub-team lead

Hi All, I have had the pleasure of chairing the live migration sub-team for the last year. Recently, as some of you will have noticed, my time has been stretched to the extent that I have started to neglect the task. Timofei Durakov has stood in for me on several occasions recently and has now

Re: [openstack-dev] [tc] open question to the candidates

On Oct 3, 2016, at 10:30 AM, gordon chung wrote: > the TC has historically been a reactive council that lets others ask for > change and acts as the final approver. do you believe the TC should be a > proactive committee that initiates change and if yes, to what scope? > more

Re: [openstack-dev] [tc] open question to the candidates

Excerpts from gordon chung's message of 2016-10-03 15:30:56 +: > hi, > > as there are many candidates this TC election, i figured i'd ask a > question to better understand the candidates from the usual sales pitch > in self-nominations. hopefully, this will give some insights into the >

Re: [openstack-dev] FYI - gate completely borked on master and newton dsvm/grenade jobs

On 2016-10-02 19:54:58 -0500 (-0500), Matt Riedemann wrote: > There was a pycparser 2.14 package update on pypi today which is making > cinder-manager db sync fail. This is making all dsvm/grenade jobs fail in > master and stable/newton. > > The upstream issue being tracked is: > >

Re: [openstack-dev] [tc] open question to the candidates

On 16-10-03 11:30 AM, gordon chung wrote: hi, as there are many candidates this TC election, i figured i'd ask a question to better understand the candidates from the usual sales pitch in self-nominations. hopefully, this will give some insights into the candidates for those who haven't voted

Re: [openstack-dev] FYI - gate completely borked on master and newton dsvm/grenade jobs

UPD: some people suggested I should update the thread about the success of the fixes. Long story short, affected projects (nova, trove) are fixed, so we consider it done. Ihar Hrachyshka wrote: UPD: @dims pushed all four into gate. (Lord be merciful.) Ihar Ihar

[openstack-dev] [glance] image import sync - Tuesdays 14:00 UTC

The voting has closed. By acclamation the weekly image import sync will occur as follows: when: Tuesdays, 14:00 UTC where: #openstack-glance duration: 20 minutes I realize this time isn't great for everyone. Since #openstack-glance is logged, I'll use "#startmeeting image import sync" and

[openstack-dev] [tc] open question to the candidates

hi, as there are many candidates this TC election, i figured i'd ask a question to better understand the candidates from the usual sales pitch in self-nominations. hopefully, this will give some insights into the candidates for those who haven't voted yet. obviously, the following is

[openstack-dev] [networking-cisco] Release Schedule

We're aiming to cut a newton & mitaka release for networking-cisco at the end of this week on 6th October. So please ensure all patches that need to be merged before then are up to date so we can review them quickly. Thanks Brad

Re: [openstack-dev] [Keystone] Project name DB length

On Mon, Oct 3, 2016 at 10:52 AM, gordon chung wrote: > > > the original thread died pretty quickly; it didn't seem like an issue to > anyone or needed fixing... if only there was a global council that > worked on such technical things :P > > ah great idea, perhaps we should call it

[openstack-dev] [puppet] weekly meeting #92

Hi Puppeteers! We'll have our weekly meeting tomorrow at 3pm UTC on #openstack-meeting-4 Here's a first agenda: https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20161004 Feel free to add topics, and any outstanding bug and patch. See you tomorrow! Thanks, --

Re: [openstack-dev] [Keystone] Project name DB length

On 28/09/2016 11:52 PM, Adrian Turjak wrote: > > Plus although there is no true official standard, most projects in > OpenStack seem to use 255 as the default for a lot of string fields. > Weirdly enough, a lot of projects seem to use 255 even for project.id, > which seeing as it's 64 in

Re: [openstack-dev] [neutron] bug deputy report

On Mon, Oct 3, 2016 at 10:15 AM, Ihar Hrachyshka wrote: > Hi all, > > I was serving as a bug deputy for the last two weeks. (Well, I planned to > serve for one week only, but then I forgot to set new deputies in the last > meeting I chaired, so the 2nd week was my punishment

[openstack-dev] [nova] next notification subteam meeting

Hi, The next notification subteam meeting will be held on 2016.10.04 17:00 UTC [1] on #openstack-meeting-4. Cheers, Gibi [1] https://www.timeanddate.com/worldclock/fixedtime.html?iso=20161004T17 __ OpenStack

[openstack-dev] [neutron] bug deputy report

Hi all, I was serving as a bug deputy for the last two weeks. (Well, I planned to serve for one week only, but then I forgot to set new deputies in the last meeting I chaired, so the 2nd week was my punishment for short memory.) There were several bugs that I did not know how to triage

Re: [openstack-dev] [Keystone] Project name DB length

On Wed, Sep 28, 2016 at 10:55 PM Adrian Turjak wrote: > I think with PKI tokens we had worse to worry about! > > At any rate, would be great to know, and if there isn't a strong reason > against it we can make project name 255 for some more flexibility. > It's nice for

Re: [openstack-dev] [all][i18n] do we need translation mark for strings in tests?

On Sat, Oct 1, 2016 at 5:24 PM Ihar Hrachyshka wrote: > Akihiro Motoki wrote: > > > Hi, > > > > I noticed strings in tests (unit tests or others) have translation marks > > (_, _LE and so on). > > Do we need translation marks for them? > > > > I don't

Re: [openstack-dev] [ironic] ironic-inspector-core team update

Thanks guys! :) Cheers, milan po 3. 10. 2016 v 10:49 odesílatel Dmitry Tantsur napsal: > The change is in effect. Thanks for your hard work Milan! > > On 09/26/2016 02:55 PM, milanisko k wrote: > > Thanks guys! :D > > > > -- > > milan > > > > po 26. 9. 2016 v 14:46

Re: [openstack-dev] [tripleo] Roles count and flavors inside Heat environment file

On Mon, Oct 03, 2016 at 02:23:08PM +0200, Marius Cornea wrote: > Hello everyone, > > In Newton we've deprecated the *-scale and *-flavor deploy command > arguments in favor of using Heat environment files. In the context of > testing the composable roles where the custom roles' node count and >

Re: [openstack-dev] FYI - gate completely borked on master and newton dsvm/grenade jobs

UPD: @dims pushed all four into gate. (Lord be merciful.) Ihar Ihar Hrachyshka wrote: Long story short, this topic should get us back to normal: https://review.openstack.org/#/q/topic:bug/1629830 We could probably also ban the version in global-requirements.txt, but I

Re: [openstack-dev] [tripleo] Roles count and flavors inside Heat environment file

On Mon, Oct 03, 2016 at 02:23:08PM +0200, Marius Cornea wrote: > Hello everyone, > > In Newton we've deprecated the *-scale and *-flavor deploy command > arguments in favor of using Heat environment files. In the context of > testing the composable roles where the custom roles' node count and >

Re: [openstack-dev] FYI - gate completely borked on master and newton dsvm/grenade jobs

Added a test commit for Designate - https://review.openstack.org/#/c/381084/ On 03/10/2016 13:31, Amrith Kumar wrote: > FWIW, this does not appear to work for Trove. To confirm I've pushed up a > trial balloon (https://review.openstack.org/#/c/381075/2). > > At least on a local sandbox it does

Re: [openstack-dev] FYI - gate completely borked on master and newton dsvm/grenade jobs

FWIW, this does not appear to work for Trove. To confirm I've pushed up a trial balloon (https://review.openstack.org/#/c/381075/2). At least on a local sandbox it does not work ... -amrith > -Original Message- > From: Ihar Hrachyshka [mailto:ihrac...@redhat.com] > Sent: Monday,

[openstack-dev] [tripleo] Roles count and flavors inside Heat environment file

Hello everyone, In Newton we've deprecated the *-scale and *-flavor deploy command arguments in favor of using Heat environment files. In the context of testing the composable roles where the custom roles' node count and flavor need to be passed inside an environment file I would like to build

Re: [openstack-dev] FYI - gate completely borked on master and newton dsvm/grenade jobs

Ihar Hrachyshka wrote: Long story short, this topic should get us back to normal: https://review.openstack.org/#/q/topic:bug/1629830 We could probably also ban the version in global-requirements.txt, but I am bad at foresight. I will let others to clean it up if

Re: [openstack-dev] FYI - gate completely borked on master and newton dsvm/grenade jobs

Long story short, this topic should get us back to normal: https://review.openstack.org/#/q/topic:bug/1629830 We could probably also ban the version in global-requirements.txt, but I am bad at foresight. I will let others to clean it up if needed. Ihar Graham wrote:

Re: [openstack-dev] FYI - gate completely borked on master and newton dsvm/grenade jobs

Also impacts designate, our dashboard, and our tempest plugin. It will probably hit our client library as well. -- Graham On 03/10/2016 12:49, Amrith Kumar wrote: > Also impacts Trove, see (for example) > > > >

Re: [openstack-dev] FYI - gate completely borked on master and newton dsvm/grenade jobs

Also impacts Trove, see (for example) http://logs.openstack.org/85/380985/1/check/gate-trove-functional-dsvm-mysql/48ae79c/logs/devstacklog.txt.gz#_2016-10-03_09_04_15_199 I have updated https://bugs.launchpad.net/trove/+bug/1629726 and marked it as impacting Trove. -amrith From: Steven Dake

Re: [openstack-dev] [magnum] Swarm Mode -- to come?

Hi Ton, I filed a high-level blueprint and assigned to you as a manager, if you have questions just ask. Implementing the new Swarm as a COE should be rather straightforward, much more than the old Swarm. Details in the BP. Thanks, Fabrizio > On Oct 3, 2016, at 9:12 AM, Ton Ngo

Re: [openstack-dev] FYI - gate completely borked on master and newton dsvm/grenade jobs

Le 03/10/2016 12:27, Sylvain Bauza a écrit : Le 03/10/2016 12:02, Sylvain Bauza a écrit : Le 03/10/2016 02:54, Matt Riedemann a écrit : There was a pycparser 2.14 package update on pypi today which is making cinder-manager db sync fail. This is making all dsvm/grenade jobs fail in

Re: [openstack-dev] FYI - gate completely borked on master and newton dsvm/grenade jobs

Le 03/10/2016 12:02, Sylvain Bauza a écrit : Le 03/10/2016 02:54, Matt Riedemann a écrit : There was a pycparser 2.14 package update on pypi today which is making cinder-manager db sync fail. This is making all dsvm/grenade jobs fail in master and stable/newton. The upstream issue being

Re: [openstack-dev] FYI - gate completely borked on master and newton dsvm/grenade jobs

Le 03/10/2016 02:54, Matt Riedemann a écrit : There was a pycparser 2.14 package update on pypi today which is making cinder-manager db sync fail. This is making all dsvm/grenade jobs fail in master and stable/newton. The upstream issue being tracked is:

Re: [openstack-dev] [mistral] Cancelling team meeting - 10/03/2016

On 3 October 2016 at 08:32, Renat Akhmerov wrote: > Hi, > > We decided to cancel today’s team meeting because most people are either > busy with release activities or on holidays. > Hi, Thanks for sending this. I just had a quick idea - maybe when we cancel the

Re: [openstack-dev] [tripleo] all OVB jobs failing on stable/newton - neutron fails to sync db

Emilien Macchi wrote: A bit of investigation drove me to a new dependency required by python-networking-cisco. I proposed the new dependency in RDO: https://review.rdoproject.org/r/#/c/2889/ "Since https://review.openstack.org/#/c/377937/ has been merged upstream, we now

Re: [openstack-dev] FYI - gate completely borked on master and newton dsvm/grenade jobs

Matt Riedemann wrote: There was a pycparser 2.14 package update on pypi today which is making cinder-manager db sync fail. This is making all dsvm/grenade jobs fail in master and stable/newton. The upstream issue being tracked is:

Re: [openstack-dev] FYI - gate completely borked on master and newton dsvm/grenade jobs

It also blocks Mistral gates. Renat Akhmerov @Nokia > On 03 Oct 2016, at 13:07, Kota TSUYUZAKI wrote: > > Swift is affected too[1] (maybe since swift is using Cryptography). When > trying to set upper constraint as pycparser<=2.13[1] in the requirements.txt, >

Re: [openstack-dev] [nova][libvirt] Lets make libvirt's domain XML canonical

On Fri, Sep 30, 2016 at 04:36:31PM +, Murray, Paul (HP Cloud) wrote: > > We have a problem migrating rescued instances that has a fix in progress based > on regenerating the xml on unrescue, see: > > https://blueprints.launchpad.net/nova/+spec/live-migrate-rescued-instances > > That might

Re: [openstack-dev] [nova][libvirt] Lets make libvirt's domain XML canonical

On Mon, Oct 03, 2016 at 10:11:34AM +0300, Timofei Durakov wrote: > Hi team, > > I agree that it's kind of strange thing that nova dumps xml definition to > the disk but doesn't use it(at least I do not aware of it). > How the proposed changed would be aligned with other drivers? The worst > case

Re: [openstack-dev] [nova][libvirt] Lets make libvirt's domain XML canonical

Timofei, On Mon, Oct 3, 2016 at 10:11 AM, Timofei Durakov wrote: > Hi team, > Taking that into account, the > question here would be: why not to store all required information(e.g. boot > order) in DB instead? I think, we definitely could do that, just like we currently

Re: [openstack-dev] [ironic] ironic-inspector-core team update

The change is in effect. Thanks for your hard work Milan! On 09/26/2016 02:55 PM, milanisko k wrote: Thanks guys! :D -- milan po 26. 9. 2016 v 14:46 odesílatel Jim Rollenhagen > napsal: // jim On Mon, Sep 26, 2016 at 5:24 AM,

Re: [openstack-dev] Magnum:

Hi Kamal. On 3 October 2016 at 09:33, kamalakannan sanjeevan < chirukamalakan...@gmail.com> wrote: > Hi All, > > I have installed Mitaka on ubuntu14.04. I have tried an all in one > installation along with cinder using dd and then creating the > cinder-volumes at /dev/loop2. The network neutron

[openstack-dev] [karbor][smaug] Weekly Meeting Cancelled (2016-10-04)

Hello everybody, The Karbor IRC meeting 2016-10-04 15:00 UTC is cancelled, welcome to join us at #openstack-karbor. --Yuval - This email and any

[openstack-dev] Magnum:

Hi All, I have installed Mitaka on ubuntu14.04. I have tried an all in one installation along with cinder using dd and then creating the cinder-volumes at /dev/loop2. The network neutron is using linuxbridge with vxlan. I am able to create instances that do not have internet reachability for

[openstack-dev] [mistral] Cancelling team meeting - 10/03/2016

Hi, We decided to cancel today’s team meeting because most people are either busy with release activities or on holidays. Stay tuned, thanks. Renat Akhmerov @Nokia __ OpenStack Development Mailing List (not for usage

  1   2   >