Re: [openstack-dev] [neutron][all] when can we drop XML support in neutronclient? Now?

> On Dec 3, 2015, at 9:48 AM, Armando M. wrote: > > > >> On 3 December 2015 at 08:33, Ihar Hrachyshka wrote: >> Akihiro Motoki wrote: >> >>> Hi, >>> >>> python-neutronclient still has XML support of Neutron API. >>> I would like to discuss when we drop XML support in neutronclient. >>> >

Re: [openstack-dev] [neutron][all] when can we drop XML support in neutronclient? Now?

Thanks all. Let's drop XML support from neutronclient! Elena already posted a patch to drop it. Akihiro 2015-12-04 1:48 GMT+09:00 Armando M. : > > > On 3 December 2015 at 08:33, Ihar Hrachyshka wrote: >> >> Akihiro Motoki wrote: >> >>> Hi, >>> >>> python-neutronclient still has XML support of N

Re: [openstack-dev] [neutron] Multiple locations for documentation of features

2015-12-05 8:40 GMT+09:00 Armando M. : > > > On 4 December 2015 at 11:22, Henry Gessau wrote: >> >> Sean M. Collins wrote: >> > I've noticed that a lot of features are now being documented as RSTs >> > inside of devref. Like the following: >> > >> > https://review.openstack.org/#/c/251859/ >> > >

Re: [openstack-dev] [Fuel] CentOS7 Merging Plan

Great progress, thank you for keeping everyone informed. On Fri, Dec 4, 2015 at 4:43 PM Dmitry Teselkin wrote: > Hello, > > Status update for Dec, 4 - we're on track. > > As there were no significant issues found during BVT / swarm test runs > on custom CentOS7 ISO it was decided to go with merg

Re: [openstack-dev] [Neutron] Rename tenant to project: discussion

On 12/04/2015 04:26 PM, Armando M. wrote: On 4 December 2015 at 10:02, Kevin Benton mailto:blak...@gmail.com>> wrote: So obviously the stuff in the client can be updated since most of that is user-facing. However, on the server side maybe we can start out by keeping all of the inte

Re: [openstack-dev] [kolla][nova] Orchiestrated upgrades in kolla

Hey, Well, example you describe is similar to a situation "what if my computer dies when I'm in the middle of an alter database". I'd argue that we should at least for start assume that operators won't do stupid things intentionally (but bad things might happen, hence step 0). I don't assume we'll

Re: [openstack-dev] [all] [tc] [ironic] Picking an official name for a subproject (ironic-inspector in this case)

+1 for baremetal-inspection On Fri, Dec 4, 2015 at 11:25 PM, Julien Danjou wrote: > On Fri, Dec 04 2015, Dmitry Tantsur wrote: > > > Do you register all 3 in keystone? What do you use as service types? > > Yes: metering, alarming and metric. > > -- > Julien Danjou > # Free Software hacker > # ht

Re: [openstack-dev] [Fuel] CentOS7 Merging Plan

Hello, Status update for Dec, 4 - we're on track. As there were no significant issues found during BVT / swarm test runs on custom CentOS7 ISO it was decided to go with merge party and merge all CentOS7 related CRs. Our CI was partially updated then and we started building ISO using production jo

Re: [openstack-dev] [neutron] Multiple locations for documentation of features

On 4 December 2015 at 11:22, Henry Gessau wrote: > Sean M. Collins wrote: > > I've noticed that a lot of features are now being documented as RSTs > > inside of devref. Like the following: > > > > https://review.openstack.org/#/c/251859/ > > > > But there are lots already present. Can someone po

Re: [openstack-dev] [Neutron] Bug deputy process

On 4 December 2015 at 15:15, Carl Baldwin wrote: > On Thu, Dec 3, 2015 at 9:29 AM, Kyle Mestery wrote: > > One concern I have is ensuring we rotate people, because it does take > some > > time, and if the same handful of rotate, they will burn out. So I > actively > > encourage more people to vo

Re: [openstack-dev] [all] [tc] [ironic] Picking an official name for a subproject (ironic-inspector in this case)

On Fri, Dec 04 2015, Dmitry Tantsur wrote: > Do you register all 3 in keystone? What do you use as service types? Yes: metering, alarming and metric. -- Julien Danjou # Free Software hacker # https://julien.danjou.info signature.asc Description: PGP signature _

Re: [openstack-dev] [Neutron] Bug deputy process

On Thu, Dec 3, 2015 at 9:29 AM, Kyle Mestery wrote: > One concern I have is ensuring we rotate people, because it does take some > time, and if the same handful of rotate, they will burn out. So I actively > encourage more people to volunteer, you don't even have to be a Neutron core > reviewer to

Re: [openstack-dev] [Performance][Proposal] Moving IRC meeting from 15:00 UTC to 16:00 UTC

Excerpts from Dina Belova's message of 2015-12-04 01:46:06 -0800: > Dear performance folks, > > There is a suggestion to move our meeting time from 15:00 UTC (Tuesdays > ) to > 16:00 UTC (also Tuesdays >

Re: [openstack-dev] [Congress] Python 3 ready

Thanks, Victor. Congrats to everyone who worked on the port =) Replacing antlr3 is an important TODO item, but IMHO separate from supporting Python 3. A Python 3 port of antlr3 was available from the antlr community so we used it, with the understanding that antlr3 needs replacing sooner rather t

Re: [openstack-dev] [Neutron] DVR + L3 HA + L2pop - Mapping out the work

Hi Assaf, Thanks for putting the list together. We can help to get the pending patches to be reviewed, if that would help. Thanks Swami -Original Message- From: Assaf Muller [mailto:amul...@redhat.com] Sent: Friday, December 04, 2015 2:46 PM To: OpenStack Development Mailing List (not fo

[openstack-dev] [Neutron] DVR + L3 HA + L2pop - Mapping out the work

There's a patch up for review to integrate DVR and L3 HA: https://review.openstack.org/#/c/143169/ Let me outline all of the work that has to happen before that patch would be useful: In order for DVR + L3 HA to work in harmony, each feature would have to be stable on its own. DVR has its share o

Re: [openstack-dev] [puppet] Config support for oslo.config.cfg.MultiStrOpt

On 12/02/2015 10:32 PM, Cody Herriges wrote: > Martin, > > I see no reason this shouldn't just be pushed into puppetlabs-inifile. > I can't actually find a real "spec" for INI file and even the Wiki > link[3] calls out that there is no actual spec. I suggest: 1/ we land https://review.opensta

Re: [openstack-dev] [kolla][nova] Orchiestrated upgrades in kolla

Michal, It looks pretty good but I want neo-style [1] upgrades. If someone rebuilds a container with a migration, I want to make sure that container isn't deployed until nova DB has been upgraded. Can you work this into your model? Regards -steve [1] https://www.youtube.com/watch?v=guVAeFs5X

[openstack-dev] [tosca-parser] [heat-translator] [heat] TOSCA-Parser 0.3.0 PyPI release

Hello Everyone, On behalf of the TOSCA-Parser team, I am pleased to announce the 0.3.0 PyPI release of tosca-parser which can be downloaded from https://pypi.python.org/pypi/tosca-parser This release includes following enhancements, · Support for nested imports – allows use of importing

Re: [openstack-dev] [Neutron][DVR]

On 4 December 2015 at 05:56, Ryan Moats wrote: > I pretty much agree with Oleg here - I'm not sure an additional tag for > defects is needed. > The idea of a DvrImpact in the commit message is interesting, but I'm not > entirely convinced - if we > do it for one sub-project, do we need to do it f

Re: [openstack-dev] [Neutron][DVR]

On 4 December 2015 at 00:44, Oleg Bondarev wrote: > > > On Thu, Dec 3, 2015 at 10:06 PM, Vasudevan, Swaminathan (PNB Roseville) < > swaminathan.vasude...@hpe.com> wrote: > >> Hi Carl, >> Sounds reasonable suggestion. >> Thanks >> Swami >> >> -Original Message- >> From: Carl Baldwin [mailt

Re: [openstack-dev] [Neutron] Rename tenant to project: discussion

On 4 December 2015 at 13:33, Neil Jerram wrote: > Really? I don't want to escalate, but I think that I'm entitled: > > > - to have an opinion on this, regardless of how much of the history I've > read > > > - to express that opinion in response to an explicit request for "any > feedback", parti

Re: [openstack-dev] [Manila] Midcycle meetup

On 11/19/2015 01:00 PM, Ben Swartzlander wrote: If you planning to attend the midcycle in any capacity, please vote your preferences here: https://www.surveymonkey.com/r/BXPLDXT The results of the survey were clear. Most people prefer the week of Jan 12-14. There was an offer to host in Ros

Re: [openstack-dev] [all] [tc] [ironic] Picking an official name for a subproject (ironic-inspector in this case)

Hi, > 1. "baremetalintrospection" - named after the process we > implement +1 for baremetal-introspection ( or inspection ? ) Cheers, Lucas __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openst

Re: [openstack-dev] [Neutron] Rename tenant to project: discussion

Really? I don't want to escalate, but I think that I'm entitled: - to have an opinion on this, regardless of how much of the history I've read - to express that opinion in response to an explicit request for "any feedback", particularly when no one else had responded to that call for nearly

Re: [openstack-dev] [Neutron] Rename tenant to project: discussion

On 4 December 2015 at 10:02, Kevin Benton wrote: > So obviously the stuff in the client can be updated since most of that is > user-facing. However, on the server side maybe we can start out by keeping > all of the internal code and DB tables the same. Then all we need to worry > about is the API

Re: [openstack-dev] [Neutron] Rename tenant to project: discussion

On 4 December 2015 at 08:46, Neil Jerram wrote: > I'm new to this discussion, but you did ask for any feedback, so ... > > On 03/12/15 18:29, Smigiel, Dariusz wrote: > > Hey Neutrinos (thanks armax for this word :), > > Keystone is planning to deprecate V2 API (again :). This time in Mitaka > [6]

Re: [openstack-dev] Announcing the OpenStack Health Dashboard

Cool!. From: Paul Michali [mailto:p...@michali.net] Sent: Friday, December 04, 2015 12:45 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] Announcing the OpenStack Health Dashboard Sweet! On Fri, Dec 4, 2015 at 3:40 PM Matthew Treinish mailto:mtr

Re: [openstack-dev] [murano] Is there blueprint to add argument collection UI for action

Tony, Here is the blueprint: https://blueprints.launchpad.net/murano/+spec/action-ui The problem is much bigger then it seems to. Action parameters are very similar to regular application properties and thus there should be a dedicated dynamic UI form (think ui.yaml) for each action describing it

[openstack-dev] [kolla][nova] Orchiestrated upgrades in kolla

Hey guys, Orchiestrated upgrades is one of our highest priorities for M in kolla, so following up after discussion on summit I'd like to suggest an approach: Instead of creating playbook called "upgrade my openstack" we will create "upgrade my nova" instead and approach to each service case by ca

[openstack-dev] [Neutron] Team meeting this Monday at 2100 UTC

Hi neutrinos, A kind reminder for next week's meeting. Being the meeting right after the milestone was cut, I'd like to take most of the hour to talk about blueprints/specs, i.e. the beefy workload that has merged, and has yet to merge. We'll be brief on announcements and bugs, and skip the othe

Re: [openstack-dev] Announcing the OpenStack Health Dashboard

Sweet! On Fri, Dec 4, 2015 at 3:40 PM Matthew Treinish wrote: > Hi Everyone, > > As some people may have seen already we've been working on creating a test > results dashboard up and running to visualize the state of the tests > running in > the gate. You can get to the dashboard here: > > http

[openstack-dev] OpenStack Developer Mailing List Digest November 28 - December 4

Perma link: http://www.openstack.org/blog/2015/12/openstack-developer-mailing-list-digest-november-20151128/ Success Bot Says * dims: cross-project, technical-debt-reduction effort pays dividends, no code left in oslo-incubator repo anymore. * dhellmann: horizn, searchlight, py

[openstack-dev] Announcing the OpenStack Health Dashboard

Hi Everyone, As some people may have seen already we've been working on creating a test results dashboard up and running to visualize the state of the tests running in the gate. You can get to the dashboard here: http://status.openstack.org/openstack-health/#/ It's still early for this project (

Re: [openstack-dev] [Neutron] Rename tenant to project: discussion

> On Dec 4, 2015, at 12:40 PM, Kyle Mestery wrote: > > On Fri, Dec 4, 2015 at 1:28 PM, Henry Gessau > wrote: > Kevin Benton mailto:blak...@gmail.com>> wrote: > > So obviously the stuff in the client can be updated since most of that is > > user-facing. However, on the s

Re: [openstack-dev] [Murano] How to debug a failed deployment?

Vahid, The main log file that is missing is murano-engine log. It is murano-engine who does the deployment. There are also no agent logs because agents are on VMs and none of them were created. >From what I see from you screenshots deployment task doesn't even reaches murano-engine. There can be

Re: [openstack-dev] [Neutron] Rename tenant to project: discussion

On Fri, Dec 4, 2015 at 1:28 PM, Henry Gessau wrote: > Kevin Benton wrote: > > So obviously the stuff in the client can be updated since most of that is > > user-facing. However, on the server side maybe we can start out by > keeping all > > of the internal code and DB tables the same. Then all w

Re: [openstack-dev] [Neutron] Rename tenant to project: discussion

Kevin Benton wrote: > So obviously the stuff in the client can be updated since most of that is > user-facing. However, on the server side maybe we can start out by keeping all > of the internal code and DB tables the same. Then all we need to worry about > is the API translation code to start. >

Re: [openstack-dev] [Performance][Proposal] Moving IRC meeting from 15:00 UTC to 16:00 UTC

+1 from me On Fri, Dec 4, 2015 at 8:16 AM, Joshua Harlow wrote: > +1 from me :) > > Dina Belova wrote: > >> Dear performance folks, >> >> There is a suggestion to move our meeting time from 15:00 UTC (Tuesdays >> ) to >> 16:00 U

Re: [openstack-dev] [neutron] Multiple locations for documentation of features

Sean M. Collins wrote: > I've noticed that a lot of features are now being documented as RSTs > inside of devref. Like the following: > > https://review.openstack.org/#/c/251859/ > > But there are lots already present. Can someone point out to me what the > criteria is for these documents? I am

Re: [openstack-dev] [nova] [python-novaclient] microversions support

+1 for Kevin's proposal. On Fri, Dec 4, 2015 at 8:37 PM, Chen CH Ji wrote: > +1 , added a doc change just now https://review.openstack.org/#/c/253644 > > -"Kevin L. Mitchell" wrote: - > To: > From: "Kevin L. Mitchell" > Date: 12/04/2015 06:25PM > Subject: Re: [openstack-dev] [nova] [

Re: [openstack-dev] [Neutron] Rename tenant to project: discussion

Somewhat off topic, but: Yeah, some of us ops still use "tenant" when talking to users because tenant prompts a "whats that mean" question from users, and then we get a chance to explain it. Users each have their own definition of "project", and when they see project they think they understand

Re: [openstack-dev] [tripleo] When to use parameters vs parameter_defaults

On 11/20/2015 06:05 PM, Ben Nemec wrote: > Thinking about this some more makes me wonder if we need a sample config > generator like oslo.config. It would work off something similar to the > capabilities map, where you would say > > SSL: > templates: > -puppet/extraconfig/tls/tls-cert-injec

Re: [openstack-dev] [all] [tc] [ironic] Picking an official name for a subproject (ironic-inspector in this case)

On Fri, Dec 4, 2015 at 7:30 AM, Thierry Carrez wrote: > Julien Danjou wrote: > > On Fri, Dec 04 2015, Dmitry Tantsur wrote: > > > >> Specifically, I'm talking about ironic-inspector, which is a auxiliary > service > >> under the bare metal program. My first assumption is to prefix with > ironic's

Re: [openstack-dev] [Neutron] Rename tenant to project: discussion

>Do you mean OpenStack developers, OpenStack customers, or OpenStack code? All of them. Lots of us still say 'tenant' because that's what it was for quite a while. However, with keystone and the other projects referring to 'projects' which have 'project_ids', it creates inconsistency when Neutron

Re: [openstack-dev] [nova] [python-novaclient] microversions support

+1 , added a doc change just now  https://review.openstack.org/#/c/253644 -"Kevin L. Mitchell" wrote: -To: From: "Kevin L. Mitchell" Date: 12/04/2015 06:25PMSubject: Re: [openstack-dev] [nova] [p

Re: [openstack-dev] [all] [tc] [ironic] Picking an official name for a subproject (ironic-inspector in this case)

On 2015-12-04 16:30:17 +0100 (+0100), Thierry Carrez wrote: > My take is to rename ironic-inspector to clouseau, the ironic inspector > from the Pink Panther series. If that comes to pass then count me in for the next Ironic mid-cycle, which will presumably just be a Peter Sellers movie marathon?

Re: [openstack-dev] [Neutron] Rename tenant to project: discussion

On 04/12/15 18:03, Kevin Benton wrote: > >The whole world says 'tenant' for the 'tenant' concept, particularly > in the context of networking. Changing to a different term is just > silly. > > Except for the rest of OpenStack. Do you mean OpenStack developers, OpenStack customers, or OpenStack co

Re: [openstack-dev] [puppet] bugreporting in puppet-openstack-integration

Thanks Emilien for fast fixing ! (both corrections are working fine, reviews updated accordingly) For additional bug reports I will use that newly created bug tracker . Enjoy the weekend, Michal -Original Message- From: Emilien Macchi [mailto:emil...@redhat.com] Sent: Friday, Decemb

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

On 12/04/2015 12:43 PM, Sean M. Collins wrote: > On Mon, Nov 30, 2015 at 07:00:07AM EST, Sean Dague wrote: >> On 11/25/2015 11:42 AM, Sean M. Collins wrote: >>> The first run for the multinode grenade job completed. >>> >>> http://logs.openstack.org/35/187235/11/experimental/gate-grenade-dsvm-neutr

Re: [openstack-dev] [Neutron] Rename tenant to project: discussion

So obviously the stuff in the client can be updated since most of that is user-facing. However, on the server side maybe we can start out by keeping all of the internal code and DB tables the same. Then all we need to worry about is the API translation code to start. Once our public-facing stuff i

Re: [openstack-dev] [Neutron] Rename tenant to project: discussion

>The whole world says 'tenant' for the 'tenant' concept, particularly in the context of networking. Changing to a different term is just silly. Except for the rest of OpenStack. Consistency is the one argument we can't use as a reason not to switch to project. Please read the blueprint and the em

Re: [openstack-dev] [ironic] RFC: stop using launchpad milestones and blueprints

2015-12-04 18:26 GMT+01:00 Doug Hellmann : > Excerpts from Dmitry Tantsur's message of 2015-12-04 17:38:43 +0100: > > Hi! > > > > As you all probably know, we've switched to reno for managing release > > notes. What it also means is that the release team has stopped managing > > milestones for us.

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

On Mon, Nov 30, 2015 at 07:00:07AM EST, Sean Dague wrote: > On 11/25/2015 11:42 AM, Sean M. Collins wrote: > > The first run for the multinode grenade job completed. > > > > http://logs.openstack.org/35/187235/11/experimental/gate-grenade-dsvm-neutron-multinode/011124b/logs/ > > > > I'm still get

Re: [openstack-dev] [puppet] bugreporting in puppet-openstack-integration

Hey Michal, Thanks for the bug-report! Let's see inline: On 12/04/2015 10:26 AM, Ptacek, MichalX wrote: > Hello, > > > > I have one general question for bug-reporting in > puppet-openstack-integration project, > > Actually I am having some issues by running all-in-one.sh script, > > > >

Re: [openstack-dev] [ironic] RFC: stop using launchpad milestones and blueprints

Excerpts from Dmitry Tantsur's message of 2015-12-04 17:38:43 +0100: > Hi! > > As you all probably know, we've switched to reno for managing release > notes. What it also means is that the release team has stopped managing > milestones for us. We have to manually open/close milestones in > laun

Re: [openstack-dev] [Fuel] Running Fuel node as non-superuser

Folks, there is another spec update, please take a look: https://review.openstack.org/#/c/243340 I'm also considering splitting the blueprint/spec into smaller pieces: 1. Non-root accounts on slave nodes. 2. Non-root user account (fueladmin) on master node. 3. Running fuel services as non-superus

Re: [openstack-dev] [nova] [python-novaclient] microversions support

On Fri, 2015-12-04 at 18:58 +0200, Andrey Kurilin wrote: > This week I added 5 patches to enable 2.7-2.11 microversions in > novaclient[1][2][3][4][5]. I'm not bragging. Just want to ask everyone > who are working on new microversions: Please, do not forget to add > support of your microversion to

Re: [openstack-dev] Documentation containing external resource links & privacy breaches

On Fri, Dec 4, 2015 at 10:46 AM, Cory Benfield wrote: > > On 4 Dec 2015, at 13:20, Anne Gentle > wrote: > > Great, thanks! This would work well for both oslosphinx and > openstackdocstheme: > > http://git.openstack.org/cgit/openstack/openstackdocstheme/ > > Anne > > > Ok, so to begin with I’ve f

[openstack-dev] [nova] [python-novaclient] microversions support

Hi stackers! This week I added 5 patches to enable 2.7-2.11 microversions in novaclient[1][2][3][4][5]. I'm not bragging. Just want to ask everyone who are working on new microversions: Please, do not forget to add support of your microversion to official Nova client. [1] - https://review.openstac

Re: [openstack-dev] Documentation containing external resource links & privacy breaches

> On 4 Dec 2015, at 13:20, Anne Gentle wrote: > > Great, thanks! This would work well for both oslosphinx and > openstackdocstheme: > > http://git.openstack.org/cgit/openstack/openstackdocstheme/ > > > Anne Ok, so to begin with I

Re: [openstack-dev] [Neutron] Rename tenant to project: discussion

I'm new to this discussion, but you did ask for any feedback, so ... On 03/12/15 18:29, Smigiel, Dariusz wrote: > Hey Neutrinos (thanks armax for this word :), > Keystone is planning to deprecate V2 API (again :). This time in Mitaka [6], > and probably forever. It will stay at least four release

[openstack-dev] [ironic] RFC: stop using launchpad milestones and blueprints

Hi! As you all probably know, we've switched to reno for managing release notes. What it also means is that the release team has stopped managing milestones for us. We have to manually open/close milestones in launchpad, if we feel like. I'm a bit tired of doing it for inspector, so I'd prefe

Re: [openstack-dev] [nova] Testing concerns around boot from UEFI spec

I think efi can boot off of fat16 as well. for vm's, we may not need fat32 support at all. Could we just remove the offending fat32 code? Thanks, Kevin From: Sean Dague [s...@dague.net] Sent: Friday, December 04, 2015 5:46 AM To: openstack-dev@lists.openst

Re: [openstack-dev] [all][infra] All tox jobs broken, don't approve changes for now (All green again!)

On 12/04/2015 10:31 AM, Andreas Jaeger wrote: Currently all tox jobs are broken in the OpenStack CI. The infra-team is fixing this right now. Please do not approve any changes until the broken patch has been reverted and all tox jobs have been updated, we'll send an email once this is done, Th

Re: [openstack-dev] [Performance][Proposal] Moving IRC meeting from 15:00 UTC to 16:00 UTC

+1 from me :) Dina Belova wrote: Dear performance folks, There is a suggestion to move our meeting time from 15:00 UTC (Tuesdays ) to 16:00 UTC (also Tuesdays

Re: [openstack-dev] [Performance][Proposal] Moving IRC meeting from 15:00 UTC to 16:00 UTC

Hi! 15-00 or 16-00 - it does not matter to me :) On Fri, Dec 4, 2015 at 11:46 AM, Dina Belova wrote: > Dear performance folks, > > There is a suggestion to move our meeting time from 15:00 UTC (Tuesdays > ) to > 16:00 UTC (also

[openstack-dev] [release] recording milestones for unmanaged projects

Release liaisons, We've had a couple of questions about handling the milestone releases for non-release:managed projects. Today in the release team meeting, we agreed that we would like to record the information about those releases, after they are cut. We also want to encourage everyone to take t

Re: [openstack-dev] [Performance][Proposal] Moving IRC meeting from 15:00 UTC to 16:00 UTC

+1 ___ Kris Lindgren Senior Linux Systems Engineer GoDaddy From: Dina Belova mailto:dbel...@mirantis.com>> Date: Friday, December 4, 2015 at 2:46 AM To: OpenStack Development Mailing List mailto:openstack-dev@lists.openstack.org>>,

Re: [openstack-dev] [all] [tc] [ironic] Picking an official name for a subproject (ironic-inspector in this case)

Please, please, please, let's use that in case we decide to have a next major release :D -- milan 2015-12-04 16:38 GMT+01:00 Dmitry Tantsur : > On 12/04/2015 04:30 PM, Thierry Carrez wrote: > >> Julien Danjou wrote: >> >>> On Fri, Dec 04 2015, Dmitry Tantsur wrote: >>> >>> Specifically, I'm talk

Re: [openstack-dev] [devstack] Devstack on wheezy

On Mon, Nov 30, 2015 at 08:38:10AM EST, Sean Dague wrote: > Wheezy support is best effort. > > liberasurecode-dev is really about to be a hard dependency for Swift, we > need it in our development toolchain. Someone (upstream) needs to > provide that as a backport to wheezy if running swift on whe

Re: [openstack-dev] [Fuel] FFE for Ubuntu bootstrap

Hi Mike and Igor, Thank you for the opinions. We already talked to Matt and he is fine with Fuel Menu commit. We will target the changes for Tuesday and will work with reviewers and Mos-Linux team to have blocker bug resolved and commits merged. Thanks, Dmitry. On Fri, Dec 4, 2015 at 2:04 PM, I

Re: [openstack-dev] [all] [tc] [ironic] Picking an official name for a subproject (ironic-inspector in this case)

On 12/04/2015 03:33 PM, Julien Danjou wrote: On Fri, Dec 04 2015, Dmitry Tantsur wrote: Specifically, I'm talking about ironic-inspector, which is a auxiliary service under the bare metal program. My first assumption is to prefix with ironic's official name, so it should be something like 'bare

Re: [openstack-dev] [all] [tc] [ironic] Picking an official name for a subproject (ironic-inspector in this case)

On 12/04/2015 04:30 PM, Thierry Carrez wrote: Julien Danjou wrote: On Fri, Dec 04 2015, Dmitry Tantsur wrote: Specifically, I'm talking about ironic-inspector, which is a auxiliary service under the bare metal program. My first assumption is to prefix with ironic's official name, so it should

Re: [openstack-dev] [all] [tc] [ironic] Picking an official name for a subproject (ironic-inspector in this case)

Julien Danjou wrote: > On Fri, Dec 04 2015, Dmitry Tantsur wrote: > >> Specifically, I'm talking about ironic-inspector, which is a auxiliary >> service >> under the bare metal program. My first assumption is to prefix with ironic's >> official name, so it should be something like 'baremetal-XXX'

[openstack-dev] [puppet] bugreporting in puppet-openstack-integration

Hello, I have one general question for bug-reporting in puppet-openstack-integration project, Actually I am having some issues by running all-in-one.sh script, Issue1) default scenario003 is not executed, as variable SCENARIO is not exported and visible in run_test.sh https://github.com/

Re: [openstack-dev] [Fuel] CentOS7 Merging Plan

Hello, According to the CentOS7 merging plan we've merged all CentOS7 CRs and are going to get our first builds in production CI. Please note that failures are possible for short period of time, please don't panic, we will keep an eye on every build to investigate and fix ASAP. We will send anoth

Re: [openstack-dev] The ceph jobs are regressed in all branches in the gate as of 12/4

On 12/04/2015 09:34 AM, Matt Riedemann wrote: > Tracking with this bug: > > https://bugs.launchpad.net/cinder/+bug/1520296 > > I suspect it was this change, or related to this change somehow: > > https://review.openstack.org/#/c/251421/ > > Since that's the only global ceph related change I can

[openstack-dev] [release] mitaka-1 development milestone

Hello everyone, The first milestone of the Mitaka development cycle, "mitaka-1", is now reached. Some OpenStack projects following the milestone-based release schedule took the opportunity to publish a development artifact, which contains all the new features and bugfixes that have been added sinc

[openstack-dev] [all] [infra] [java] Seeking java mirror person

Hey everyone! A few months ago, there was a conversation in #openstack-infra, where _someone_ asked for a maven repository mirror to speed up, and stabilize, any java builds. Unfortunately, I can't remember for who that was, and my grep-foo is (apparently) weak. Could the interested party please p

Re: [openstack-dev] [glance] Auth_version from 'old style' URLs in the database

On 03/12/15 16:24 +, Bunting, Niall wrote: Hi, Currently glance will use an auth_url if in the database. Eg. 10.0.0.8:5000/v2.0 However glance currently takes the auth_version from the config files. Therefore this can lead to a mismatch of keystone version to be used between the url and the

Re: [openstack-dev] [nova][docs][api] Propose Virtual Nova API Doc Sprint on Dec 8 and 9

Just reminder the event which close the time, the virtual doc sprint is right next week. Welcome to join us! 2015-11-11 20:51 GMT+08:00 Alex Xu : > Hi, > > At nova api subteam weekly meeting, we decided hold 2 days virtual doc > sprint to help the Nova API document. The initial proposed date is D

Re: [openstack-dev] [nova][bugs] Weekly Status Report

Below are the bug stats of the week "Mitaka R-18". Increases/decreases compared to "Mitaka R-20" are in parantheses. (I missed the mail for the week Mitaka R-19) Stats = New bugs which are *not* assigned to any subteam count: 12 (-18)

[openstack-dev] The ceph jobs are regressed in all branches in the gate as of 12/4

Tracking with this bug: https://bugs.launchpad.net/cinder/+bug/1520296 I suspect it was this change, or related to this change somehow: https://review.openstack.org/#/c/251421/ Since that's the only global ceph related change I can find in the last 24 hours. Otherwise it could be a regression

Re: [openstack-dev] [all] [tc] [ironic] Picking an official name for a subproject (ironic-inspector in this case)

On Fri, Dec 04 2015, Dmitry Tantsur wrote: > Specifically, I'm talking about ironic-inspector, which is a auxiliary service > under the bare metal program. My first assumption is to prefix with ironic's > official name, so it should be something like 'baremetal-XXX' or 'baremetal > XXX'. Is it cor

Re: [openstack-dev] [nova] Contribution to improve Nova's config option space

Esra Celik wrote on 12/04/2015 02:08:50 PM: > From: Esra Celik > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 12/04/2015 02:09 PM > Subject: Re: [openstack-dev] [nova] Contribution to improve Nova's > config option space > > Thanks Markus, > > I started with

Re: [openstack-dev] openstackdocstheme to be considered (very) harmful for your generated sphinx docs

On Fri, Dec 4, 2015 at 8:09 AM, Thomas Goirand wrote: > Hi, > > I've investigated a bit the openstackdocstheme, and tried to remove some > of the (numerous) javascript with external references. And it's *very* > ugly: it's full of google stuff, random CDN and so on. > > I absolutely want to addre

[openstack-dev] openstackdocstheme to be considered (very) harmful for your generated sphinx docs

Hi, I've investigated a bit the openstackdocstheme, and tried to remove some of the (numerous) javascript with external references. And it's *very* ugly: it's full of google stuff, random CDN and so on. Not only this, but generated docs could potentially do call some of these objects without usin

[openstack-dev] [nova] Nova Mitaka-1 Update and Nova Blueprint Freeze Exceptions

Hi, Here are a few reminders around the Mitaka release, and info about the blueprint freeze exception process. Dates - January 21st: Nova non-priority feature freeze (Thats the deadline for merging the code into master) December 8th and 9th: Virtual API document sprint http://lists.openstac

Re: [openstack-dev] [Neutron][DVR]

I pretty much agree with Oleg here - I'm not sure an additional tag for defects is needed. The idea of a DvrImpact in the commit message is interesting, but I'm not entirely convinced - if we do it for one sub-project, do we need to do it for all sub-projects and then what does that turn into? I'

Re: [openstack-dev] [fuel] UI experience

We tend to agree with you, guys, so the appropriated bug created. This annoying behavior will be fixed in this iteration. Best regards, Morozova Alexandra Software Developer, Mirantis, Inc. Skype: anarchistkasan #MorAle +48 514501223 *Mirantis Poland

Re: [openstack-dev] [Performance][Proposal] Moving IRC meeting from 15:00 UTC to 16:00 UTC

Apologies to those who get this twice - I'm fighting with mail clients/servers this morning (and I'm pretty sure I'm losing) As a US person, I'm going to vote -1 on moving to 1600 UTC on Tuesdays - I already have too many other meetings stacked up in this slot... Ryan Moats (regXboi) Dina Belova

Re: [openstack-dev] [nova] Testing concerns around boot from UEFI spec

On 12/04/2015 08:34 AM, Daniel P. Berrange wrote: > On Fri, Dec 04, 2015 at 07:43:41AM -0500, Sean Dague wrote: >> Can someone explain the licensing issue here? The Fedora comments make >> this sound like this is something that's not likely to end up in distros. > > The EDK codebase contains a FAT

[openstack-dev] [all] [tc] [ironic] Picking an official name for a subproject (ironic-inspector in this case)

Hi everyone! I'd like to get guidance on how to pick an official name (e.g. appearing in keystone catalog or used in API versioning headers) for a subproject of an official project. Specifically, I'm talking about ironic-inspector, which is a auxiliary service under the bare metal program. M

Re: [openstack-dev] [fuel] UI experience

Hi, that's great to know about this new button behaviour, because I was going to file a bug few days ago when I was not able to find "Stop" button on UI. But then I updated to a more recent ISO and the button "appeared" again. Now I know what that was, thank you. And I can't tell that my own exper

[openstack-dev] [python-novaclient] history of virtual-interface commands

Hi stackers! I have found code in novaclient related to virtual-interfaces extension[1], but there are no cli commands for it. Since rackspace docs include reference to `virtual-interface-list` command[2], I wonder, is there a reason for which commands related to virtual-interfaces are missed from

Re: [openstack-dev] [nova] Testing concerns around boot from UEFI spec

On Fri, Dec 04, 2015 at 07:43:41AM -0500, Sean Dague wrote: > Can someone explain the licensing issue here? The Fedora comments make > this sound like this is something that's not likely to end up in distros. The EDK codebase contains a FAT driver which has a license that forbids reusing the code

Re: [openstack-dev] [puppet] proposing Sofer Athlan Guyot part of puppet-keystone core team

Hi, Thanks everyone for you support. Emilien Macchi writes: > Hi, > > For some months, Puppet OpenStack group has been very lucky to have > Sofer working with us. > He became a huge contributor to puppet-keystone, he knows the module > perfectly and wrote insane amount of code recently, to brin

Re: [openstack-dev] Documentation containing external resource links & privacy breaches

On Fri, Dec 4, 2015 at 5:03 AM, Cory Benfield wrote: > > > On 4 Dec 2015, at 10:06, Thomas Goirand wrote: > > > > That's actually a very good idea, I didn't think it was possible. Could > > you explain a bit more how this kind of patch would look like? > > Sure. Rather than explain and take the

Re: [openstack-dev] [Nova] How to check changes waiting for review

John, Thanks for the detailed answer and the page links. Also your reviews page seems very useful Regards, Esra Çelik - Orijinal Mesaj - > Kimden: "John Garbutt" > Kime: "OpenStack Development Mailing List (not for usage questions)" > > Gönderilenler: 4 Aralık Cuma 2015 15:00:05

  1   2   >