Re: [openstack-dev] [Kuryr][Magnum] - Kuryr nested containers and Magnum Integration

On Fri, Jun 24, 2016 at 7:42 PM, Hongbin Lu wrote: > > > > > *From:* Vikas Choudhary [mailto:choudharyvika...@gmail.com] > *Sent:* June-22-16 3:58 AM > *To:* OpenStack Development Mailing List (not for usage questions) > *Subject:* Re: [openstack-dev] [Kuryr][Magnum] -

Re: [openstack-dev] [stable][all] Tagging kilo-eol for "the world"

Removing the pbr branch should be fine - it was an exceptional thing to have that branch in the first place - pbr is consumed by releases only, and due to its place in the dependency graph is very very very hard to pin or cap. -Rob On 25 June 2016 at 12:37, Tony Breeds

Re: [openstack-dev] [stable][all] Tagging kilo-eol for "the world"

On Fri, Jun 24, 2016 at 04:36:03PM -0700, Sumit Naiksatam wrote: > Hi Tony, Thanks for your response, and no worries! We can live with > the kilo-eol tag, no need to try to delete it. And as you suggested, > we can add a second eol tag when we actually EoL this branch. > > As regards reviving the

[openstack-dev] [Horizon] xstatic publishing update - broken xstatic-angular-bootstrap

Hi folks, I released a couple of broken xstatic-angular-bootstrap packages to pypi yesterday - 0.11.0.4 and 0.11.0.5. There was to be an automated release of 0.11.0.6 through openstack-release, but I've abandoned that as it contained the same breakage. I've performed an emergency direct upload of

Re: [openstack-dev] [stable][all] Tagging kilo-eol for "the world"

Hi Tony, Thanks for your response, and no worries! We can live with the kilo-eol tag, no need to try to delete it. And as you suggested, we can add a second eol tag when we actually EoL this branch. As regards reviving the deleted branches, would a bug have to be created somewhere to track this,

[openstack-dev] [ironic] Separate maintenance mode for Ironic-found faults

Hi all, At the design summit in Austin, I took an action item after the anomaly resolution to file a spec to separate operator-set and ironic-set maintenance. Now that CI testing is done and we're making progress on other priorities, I took time today to submit the RFE bug and a draft spec.

Re: [openstack-dev] [stable][all] Tagging kilo-eol for "the world"

On Fri, Jun 24, 2016 at 11:20:12AM -0700, Sumit Naiksatam wrote: > Hi, I had earlier requested in this thread that the stable/kilo branch > for the following repos be not deleted: > > > openstack/group-based-policy > > openstack/group-based-policy-automation > > openstack/group-based-policy-ui >

Re: [openstack-dev] [cinder] No middle-man - when does/will Nova directly connect iSCSI volumes?

Does QEMU support hardware initiators? iSER? No, this is only for case where you're doing pure software based iSCSI client connections. If we're relying on local hardware that's a different story. We regularly fix issues with iSCSI attaches in the release cycles of OpenStack, because it's

Re: [openstack-dev] [horizon] npm lint and test problems in gate

On 2016-06-24 19:12:01 + (+), Borland, Matt wrote: > It seems that the npm-run jobs are both passing Jenkins even when the tests > themselves fail. I'm not sure why that is, but Cores in particular: > > Please run "npm run lint && npm run test" before you +2 (or +1) anything. > This

[openstack-dev] [Heat] Tripleo holding on to old, bad data

A coworker and I have both had trouble recovering from failed overcloud deploys. I've wiped out whatever data I can, but, even with nothing in the Heat Database, doing an openstack overcloud deploy seems to be looking for a specific Nova server by UUID: heat resource-show

Re: [openstack-dev] [fuel][plugins][ovs]

Thanks, -Ankit From: Andrew Woodward [mailto:xar...@gmail.com] Sent: Friday, June 24, 2016 12:20 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [fuel][plugins][ovs] You can track the fuel version supported

[openstack-dev] [gnocchi] profiling and benchmarking 2.1.x

hi, i realised i didn't post this beyond IRC, so here are some initial numbers for some performance/benchmarking i did on Gnocchi. http://www.slideshare.net/GordonChung/gnocchi-profiling-21x as a headsup, the data above is using Ceph and with pretty much a default configuration. i'm currently

Re: [openstack-dev] [vitrage][aodh] Notifications about aodh alarm state changes

On 24/06/2016 9:58 AM, Julien Danjou wrote: > On Thu, Jun 23 2016, Afek, Ifat (Nokia - IL) wrote: > >> I understood that during Aodh-Vitrage design session in Austin, you had a >> discussion about Vitrage need for notifications about Aodh alarm state >> changes. >> Did you have a chance to

Re: [openstack-dev] [fuel][plugins][ovs]

You can track the fuel version supported by examining the metadata.yaml in the root of the plugin repo. Since there is no stable/7.0 tag the last point before metadata.yaml was changed to 8.0 is https://github.com/openstack/fuel-plugin-ovs/tree/3776734a7b93ac440aa7b2e730d743b8510aac25 You can try

[openstack-dev] [horizon] npm lint and test problems in gate

Horizoneers, It seems that the npm-run jobs are both passing Jenkins even when the tests themselves fail. I'm not sure why that is, but Cores in particular: Please run "npm run lint && npm run test" before you +2 (or +1) anything. This ensures that we don't pollute master with broken

Re: [openstack-dev] [stable][all] Tagging kilo-eol for "the world"

Hi, I had earlier requested in this thread that the stable/kilo branch for the following repos be not deleted: > openstack/group-based-policy > openstack/group-based-policy-automation > openstack/group-based-policy-ui > openstack/python-group-based-policy-client and the request was ack’ed by

Re: [openstack-dev] [release][reno][infra] merging tags between branches is confusing our release notes

Excerpts from Doug Hellmann's message of 2016-06-08 14:13:44 -0400: > tl;dr: The switch from pre-versioning to post-versioning means that > sometimes master appears to be older than stable/$previous, so we > merge "final" tags from stable/$previous into master to make up for > it. This introduces

Re: [openstack-dev] [QA][Infra] Newton Code Sprint

I added a 'topics' section to the wiki. Infra has many contributors and many projects, it's valuable to know what we'll be focusing on at the sprint so people can know ahead of time if they should go. For me, I'm interested in hacking on infracloud and the hardening aspect of the puppet/ansible

[openstack-dev] [fuel][plugins][ovs]

Hello, I'm trying to install ovs with dpdk 2.4/2.2 plugin for openstack kilo mirantis 7.0. I'm not sure if there is a compatible version for that on the github openstack/fuel-plugin-ovs . If there is one, could you upload the plugin. Thanks [banner11] Ankit Chilakapaty Engineer - IT

Re: [openstack-dev] [stable][all] Tagging kilo-eol for "the world"

On 06/24/2016 02:09 PM, Joshua Hesketh wrote: Hi all, I have completed removing stable/kilo branches from the projects listed [0]*. There are now 'kilo-eol' tags in place at the sha's where the branches were. *There are a couple of exceptions. oslo-incubator was listed but is an unmaintained

[openstack-dev] [Magnum]Midcycle

Hi all, The Magnum midcycle will be held in Aug 4 - 5 at Austin. Below is the link to register. Hope to see you all there. https://www.eventbrite.com/e/magnum-midcycle-tickets-26245489967 Best regards, Hongbin __ OpenStack

Re: [openstack-dev] [neutron] [classifier] Spec detailing both approaches

Thanks Vikram! I’ve added my approach to the spec and made it compatible with spec docs/py27, I’ll submit it now so part of the community can still take a look before the end of the week :) Best regards, Igor. From: Vikram Choudhary [mailto:viks...@gmail.com] Sent: Friday, June 24, 2016 3:09

Re: [openstack-dev] [Fuel] Merge IRC channels

There is also #fuel-devops I never liked having all the channels, so +1 On Fri, Jun 24, 2016 at 4:25 AM Anastasia Urlapova wrote: > Vova, > please don't forget merge #fuel-qa into a #fuel > > On Fri, Jun 24, 2016 at 1:55 PM, Vladimir Kozhukalov < >

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Excerpts from Zhipeng Huang's message of 2016-06-24 18:15:30 +0200: > Hi Clint and Amrith, > > Are you guys already working on the proposal ? Is there any public access > to see the first draft ? > I've started writing something up, and I hope to submit it for review next week.

[openstack-dev] [nova][scheduler] Next scheduler subteam meeting

The next meeting for the Nova Scheduler subteam will be Monday, June 27 at 1400UTC http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160627T14 The agenda is here: https://wiki.openstack.org/wiki/Meetings/NovaScheduler Please add any items you would like to discuss to the agenda

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

On 06/24/2016 11:48 AM, Doug Hellmann wrote: > Excerpts from Dmitry Tantsur's message of 2016-06-24 10:59:14 +0200: >> On 06/23/2016 11:21 PM, Clark Boylan wrote: >>> On Thu, Jun 23, 2016, at 02:15 PM, Doug Hellmann wrote: Excerpts from Thomas Goirand's message of 2016-06-23 23:04:28 +0200:

Re: [openstack-dev] [all] Proposal: Architecture Working Group

Hi Clint and Amrith, Are you guys already working on the proposal ? Is there any public access to see the first draft ? On Wed, Jun 22, 2016 at 11:23 PM, Mike Perez wrote: > On 10:27 Jun 20, Clint Byrum wrote: > > Excerpts from Doug Wiegley's message of 2016-06-20 10:40:56

Re: [openstack-dev] [grenade] upgrades vs rootwrap

On 2016-06-24 06:47:08 -0400 (-0400), Sean Dague wrote: [...] > When you upgrade Apache, you don't have to change your config > files. [...] *cough* (2.4) *cough* But it still highlights your point. There's been basically one Apache transition in recent history where a majority of people running

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

Excerpts from Daniel P. Berrange's message of 2016-06-24 09:25:35 +0100: > On Thu, Jun 23, 2016 at 11:04:28PM +0200, Thomas Goirand wrote: > > On 06/23/2016 06:11 PM, Doug Hellmann wrote: > > > I'd like for the community to set a goal for Ocata to have Python > > > 3 functional tests running for

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

On 23/06/16 12:11 -0400, Doug Hellmann wrote: Excerpts from Thomas Goirand's message of 2016-06-22 10:49:01 +0200: On 06/22/2016 09:18 AM, Victor Stinner wrote: > Hi, > > Current status: only 3 projects are not ported yet to Python 3: > > * nova (76% done) > * trove (42%) > * swift (0%) > >

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

Excerpts from Dmitry Tantsur's message of 2016-06-24 10:59:14 +0200: > On 06/23/2016 11:21 PM, Clark Boylan wrote: > > On Thu, Jun 23, 2016, at 02:15 PM, Doug Hellmann wrote: > >> Excerpts from Thomas Goirand's message of 2016-06-23 23:04:28 +0200: > >>> On 06/23/2016 06:11 PM, Doug Hellmann

Re: [openstack-dev] [TripleO] Proposal for a new tool: dlrn-repo

I'm just going to take this opportunity to point out that when RDO moved the dlrn repos this week the tool did not break because requests is smarter than curl. Also, it would have been super nice to have exactly one place to update the repo locations instead of at least 3. On 06/13/2016 03:29

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

On 06/24/2016 10:10 AM, Clint Byrum wrote: > Excerpts from Amrith Kumar's message of 2016-06-24 10:13:37 +: >> >>> -Original Message- >>> From: Doug Hellmann [mailto:d...@doughellmann.com] >>> Sent: Thursday, June 23, 2016 5:16 PM >>> To: openstack-dev

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

Excerpts from Clint Byrum's message of 2016-06-24 08:10:18 -0700: > Excerpts from Amrith Kumar's message of 2016-06-24 10:13:37 +: > > > > > -Original Message- > > > From: Doug Hellmann [mailto:d...@doughellmann.com] > > > Sent: Thursday, June 23, 2016 5:16 PM > > > To: openstack-dev

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

Excerpts from Amrith Kumar's message of 2016-06-24 10:13:37 +: > > > -Original Message- > > From: Doug Hellmann [mailto:d...@doughellmann.com] > > Sent: Thursday, June 23, 2016 5:16 PM > > To: openstack-dev > > Subject: Re: [openstack-dev] [all]

Re: [openstack-dev] [TripleO] CI package build issues

A quick update on this. It appears that https://review.rdoproject.org/r/1500 did indeed resolve the issue. There have been no hits on the logstash query [1] since that merged. [1]

Re: [openstack-dev] [cinder] No middle-man - when does/will Nova directly connect iSCSI volumes?

On Fri, Jun 24, 2016 at 08:05:38AM -0600, John Griffith wrote: > On Fri, Jun 24, 2016 at 2:19 AM, Daniel P. Berrange > wrote: > > > On Thu, Jun 23, 2016 at 09:09:44AM -0700, Walter A. Boring IV wrote: > > > > > > volumes connected to QEMU instances eventually become directly

Re: [openstack-dev] [Kuryr][Magnum] - Kuryr nested containers and Magnum Integration

From: Vikas Choudhary [mailto:choudharyvika...@gmail.com] Sent: June-22-16 3:58 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Kuryr][Magnum] - Kuryr nested containers and Magnum Integration Hi Eli Qiao, Please find my responses inline. On

Re: [openstack-dev] [neutron] [classifier] Spec detailing both approaches

Hi Igor/Cathy/Louis, Thanks for driving this effort. Will certainly help with the review! Thanks Vikram On Fri, Jun 24, 2016 at 5:47 PM, Duarte Cardoso, Igor < igor.duarte.card...@intel.com> wrote: > Hi Cathy, Louis, > > > > I'll reupload the Neutron spec today to openstack/neutron-specs along

Re: [openstack-dev] [cinder] No middle-man - when does/will Nova directly connect iSCSI volumes?

On Fri, Jun 24, 2016 at 2:19 AM, Daniel P. Berrange wrote: > On Thu, Jun 23, 2016 at 09:09:44AM -0700, Walter A. Boring IV wrote: > > > > volumes connected to QEMU instances eventually become directly connected? > > > > > Our long term goal is that 100% of all network

Re: [openstack-dev] [vitrage][aodh] Notifications about aodh alarm state changes

On Thu, Jun 23 2016, Afek, Ifat (Nokia - IL) wrote: > I understood that during Aodh-Vitrage design session in Austin, you had a > discussion about Vitrage need for notifications about Aodh alarm state > changes. > Did you have a chance to think about it since, and to check how this can be >

Re: [openstack-dev] [openstack-ansible] Change of default database collation

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 06/24/2016 12:07 AM, Jimmy McCrory wrote: > The question then comes to how to best handle upgrades from Mitaka to Newton. > Any input for the current proposal[3] from anyone that may have experience > with any project's database migration

Re: [openstack-dev] [grenade] upgrades vs rootwrap

On Fri, 24 Jun 2016 at 21:04 Sean Dague wrote: > On 06/24/2016 05:19 AM, Daniel P. Berrange wrote: > > On Fri, Jun 24, 2016 at 11:12:27AM +0200, Thierry Carrez wrote: > >> No perfect answer here... I'm hesitating between (0), (1) and (4). (4) > is > >> IMHO the right solution,

[openstack-dev] [neutron] [classifier] Spec detailing both approaches

Hi Cathy, Louis, I'll reupload the Neutron spec today to openstack/neutron-specs along with the rst file and the neutron-classifier-inspired approach detailed, replacing [1] and [2] from openstack/neutron, is that okay? Review from the Neutron community, interested consumers and

Re: [openstack-dev] [mistal] Mistral logo ideas?

De : REZMERITA Ala OBS/OCB Envoyé : vendredi 24 juin 2016 14:07 À : OpenStack Development Mailing List (not for usage questions) Objet : RE:[openstack-dev] [mistal] Mistral logo ideas? Hi folks, maybe something based on compass rose?

Re: [openstack-dev] [stable][all] Tagging kilo-eol for "the world"

Hi all, I have completed removing stable/kilo branches from the projects listed [0]*. There are now 'kilo-eol' tags in place at the sha's where the branches were. *There are a couple of exceptions. oslo-incubator was listed but is an unmaintained project so no further action was required. Tony

Re: [openstack-dev] [Puppet] Suggestions for Dynamic enabling of SRIOV nic agent

I would probably create a custom fact to identify which ones have sriov capable NICs and use that to selectively enable installation of the correct packages, setup aggregates, etc. On Fri, Jun 24, 2016 at 7:19 AM, Sanjay Upadhyay wrote: > Hello Folks, > > Wondering what is

Re: [openstack-dev] [mistal] Mistral logo ideas?

Maybe smth like this [image: Inline image 1] On Fri, Jun 24, 2016 at 2:18 PM, Ilya Kutukov wrote: > Here is top-down projection > https://www.the-blueprints.com/blueprints-depot/ships/ships-france/nmf-mistral-l9013.png > > On Fri, Jun 24, 2016 at 2:17 PM, Ilya Kutukov

Re: [openstack-dev] [Fuel] Merge IRC channels

Vova, please don't forget merge #fuel-qa into a #fuel On Fri, Jun 24, 2016 at 1:55 PM, Vladimir Kozhukalov < vkozhuka...@mirantis.com> wrote: > Nice. #fuel-infra is to merged as well. > > Vladimir Kozhukalov > > On Fri, Jun 24, 2016 at 1:50 PM, Aleksandra Fedorova < > afedor...@mirantis.com>

Re: [openstack-dev] [mistal] Mistral logo ideas?

Here is top-down projection https://www.the-blueprints.com/blueprints-depot/ships/ships-france/nmf-mistral-l9013.png On Fri, Jun 24, 2016 at 2:17 PM, Ilya Kutukov wrote: > Look, Mistral landing markup (white stripes and circles with numbers) > looks like tasks queue: >

[openstack-dev] [Puppet] Suggestions for Dynamic enabling of SRIOV nic agent

Hello Folks, Wondering what is the best approach to dynamically generating info of SRIOV capable hosts in a cluster? The problem is, user want to deploy sriov-nic-agent on compute nodes, with mixed set of h/w configuration, ie set of compute nodes which do not have SR-IOV nics and a set of nodes

Re: [openstack-dev] [mistal] Mistral logo ideas?

Look, Mistral landing markup (white stripes and circles with numbers) looks like tasks queue: https://patriceayme.files.wordpress.com/2014/05/mistral.jpg On Fri, Jun 24, 2016 at 12:55 PM, Hardik wrote: > +1 :) > > > On Friday 24 June 2016 03:08 PM, Nikolay

Re: [openstack-dev] [grenade] upgrades vs rootwrap

On 06/24/2016 05:19 AM, Daniel P. Berrange wrote: > On Fri, Jun 24, 2016 at 11:12:27AM +0200, Thierry Carrez wrote: >> No perfect answer here... I'm hesitating between (0), (1) and (4). (4) is >> IMHO the right solution, but it's a larger change for downstream. (1) is a >> bit of a hack, where we

Re: [openstack-dev] [Fuel] Merge IRC channels

Nice. #fuel-infra is to merged as well. Vladimir Kozhukalov On Fri, Jun 24, 2016 at 1:50 PM, Aleksandra Fedorova wrote: > And +1 for #fuel-infra > > As of now it will be more useful if infra issues related to project will > be visible for project developers. We don't

Re: [openstack-dev] [Fuel] Merge IRC channels

Ok, let's then start from merger of #fuel-dev #fuel-python #fuel-ui #fuel-library into a single channel #fuel. #fuel-infra is to stay separate for a while. Vladimir Kozhukalov On Fri, Jun 24, 2016 at 1:41 PM, Andrew Maksimov wrote: > +1 for merging #fuel #fuel-dev

Re: [openstack-dev] [Fuel] Merge IRC channels

And +1 for #fuel-infra As of now it will be more useful if infra issues related to project will be visible for project developers. We don't have much infra-related traffic on IRC for now, and we will be able to split again if we got it. On Fri, Jun 24, 2016 at 1:26 PM, Vladimir Kozhukalov <

Re: [openstack-dev] [grenade] upgrades vs rootwrap

On 06/24/2016 05:12 AM, Thierry Carrez wrote: > Angus Lees wrote: >> [...] >> None of these are great, but: >> >> Possibility 1: Backdoor rootwrap >> >> However if we assume rootwrap already exists then we _could_ rollout a >> new version of oslo.rootwrap that contains a backdoor that allows >>

Re: [openstack-dev] [Fuel] Merge IRC channels

+1 for this, #fuel-ui should also be merged there I think. 2016-06-24 13:26 GMT+03:00 Vladimir Kozhukalov : > Dear colleagues, > > We have a few IRC channels but the level of activity there is quite low. > > #fuel > #fuel-dev > #fuel-python > #fuel-infra > > My

Re: [openstack-dev] [Fuel] Merge IRC channels

+1 for merging #fuel #fuel-dev #fuel-python and #fuel-library to #fuel. Not sure about #fuel-infra though, one of the purposes of #fuel-infra - support requests to infra team, I think #fuel channel will be too noisy if we redirect all support requests to it. Regards, Andrey On Fri, Jun 24,

[openstack-dev] [Fuel] Merge IRC channels

Dear colleagues, We have a few IRC channels but the level of activity there is quite low. #fuel #fuel-dev #fuel-python #fuel-infra My suggestion is to merge all these channels into a single IRC channel #fuel. Other #fuel-* channels are to be deprecated. What do you think of this? Vladimir

Re: [openstack-dev] [nova][pci-passthrough] definitely specify VFIO driver as the host PCI driver for passthrough

On 2016年06月24日 16:55, Daniel P. Berrange wrote: On Fri, Jun 24, 2016 at 04:52:31PM +0800, Chen Fan wrote: On 2016年06月24日 16:20, Daniel P. Berrange wrote: On Fri, Jun 24, 2016 at 12:27:57PM +0800, Chen Fan wrote: hi all, in openstack, we can use the pci passthrough feature now, refer

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

> -Original Message- > From: Doug Hellmann [mailto:d...@doughellmann.com] > Sent: Thursday, June 23, 2016 5:16 PM > To: openstack-dev > Subject: Re: [openstack-dev] [all] Status of the OpenStack port to Python 3 > [... snip ...] > > Let's see what

Re: [openstack-dev] [mistal] Mistral logo ideas?

+1 :) On Friday 24 June 2016 03:08 PM, Nikolay Makhotkin wrote: I like the idea of the logo being a stylized wind turbine. Perhaps it could be a turbine with a gust of wind. Then we can show that Mistral harnesses the power of the wind :-) I like this idea! Combine

Re: [openstack-dev] [mistal] Mistral logo ideas?

> > I like the idea of the logo being a stylized wind turbine. Perhaps it > could be > a turbine with a gust of wind. Then we can show that Mistral harnesses the > power of the wind :-) I like this idea! Combine Mistral functionality symbol with wind :) -- Best Regards, Nikolay

Re: [openstack-dev] [grenade] upgrades vs rootwrap

On Fri, Jun 24, 2016 at 11:12:27AM +0200, Thierry Carrez wrote: > Angus Lees wrote: > > [...] > > None of these are great, but: > > > > Possibility 1: Backdoor rootwrap > > > > However if we assume rootwrap already exists then we _could_ rollout a > > new version of oslo.rootwrap that contains

Re: [openstack-dev] [grenade] upgrades vs rootwrap

Angus Lees wrote: [...] None of these are great, but: Possibility 1: Backdoor rootwrap However if we assume rootwrap already exists then we _could_ rollout a new version of oslo.rootwrap that contains a backdoor that allows privsep-helper to be run as root for any context, without the need to

Re: [openstack-dev] [neutron][qos] Egress minimum bandwidth assurance

Hello: Ichihara, thank you for your answer. It was just a test to find out how to setup correctly the egress traffic shaping. I was facing this situation and I found the problem: I was using bridges with datapath_type = netdev, instead of system. That was the main problem. Now I can correctly

Re: [openstack-dev] [mistal] Mistral logo ideas?

On 22 June 2016 at 06:35, Renat Akhmerov wrote: > Hi, > > We’d like to finally come up with a logo for Mistral and it’d be cool to > hear some ideas from the community. > > Some ideas from me: > • A picture of a graph (but the point is that it must be very very

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

On 06/23/2016 11:21 PM, Clark Boylan wrote: On Thu, Jun 23, 2016, at 02:15 PM, Doug Hellmann wrote: Excerpts from Thomas Goirand's message of 2016-06-23 23:04:28 +0200: On 06/23/2016 06:11 PM, Doug Hellmann wrote: I'd like for the community to set a goal for Ocata to have Python 3 functional

Re: [openstack-dev] [nova][pci-passthrough] definitely specify VFIO driver as the host PCI driver for passthrough

On Fri, Jun 24, 2016 at 04:52:31PM +0800, Chen Fan wrote: > > > On 2016年06月24日 16:20, Daniel P. Berrange wrote: > > On Fri, Jun 24, 2016 at 12:27:57PM +0800, Chen Fan wrote: > > > hi all, > > > in openstack, we can use the pci passthrough feature now, refer to > > >

Re: [openstack-dev] [openstack-ansible] L3HA problem

> Le 22 juin 2016 à 19:40, Assaf Muller a écrit : > > On Wed, Jun 22, 2016 at 12:02 PM, fabrice grelaud > > wrote: >> >> Le 22 juin 2016 à 17:35, fabrice grelaud a >> écrit :

Re: [openstack-dev] [nova][pci-passthrough] definitely specify VFIO driver as the host PCI driver for passthrough

On 2016年06月24日 16:20, Daniel P. Berrange wrote: On Fri, Jun 24, 2016 at 12:27:57PM +0800, Chen Fan wrote: hi all, in openstack, we can use the pci passthrough feature now, refer to https://wiki.openstack.org/wiki/Pci_passthrough but we can't definitely specify the host pci

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

On Thu, Jun 23, 2016 at 10:08:22AM +0200, Sylvain Bauza wrote: > > > Le 23/06/2016 02:42, Tony Breeds a écrit : > > On Wed, Jun 22, 2016 at 12:13:21PM +0200, Victor Stinner wrote: > > > Le 22/06/2016 à 10:49, Thomas Goirand a écrit : > > > > Do you think it looks like possible to have Nova

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

Le 22/06/2016 à 09:18, Victor Stinner a écrit : Current status: only 3 projects are not ported yet to Python 3: * nova (76% done) * trove (42%) * swift (0%) If you want to help, please review my patches! I sent patches to these projects. Nova: https://review.openstack.org/#/c/332686/

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

On Thu, Jun 23, 2016 at 11:04:28PM +0200, Thomas Goirand wrote: > On 06/23/2016 06:11 PM, Doug Hellmann wrote: > > I'd like for the community to set a goal for Ocata to have Python > > 3 functional tests running for all projects. > > > > As Tony points out, it's a bit late to have this as a

Re: [openstack-dev] [nova][pci-passthrough] definitely specify VFIO driver as the host PCI driver for passthrough

On Fri, Jun 24, 2016 at 12:27:57PM +0800, Chen Fan wrote: > hi all, > in openstack, we can use the pci passthrough feature now, refer to > https://wiki.openstack.org/wiki/Pci_passthrough > but we can't definitely specify the host pci driver is LEGACY_KVM or > newer VFIO, > new

Re: [openstack-dev] [cinder] No middle-man - when does/will Nova directly connect iSCSI volumes?

On Thu, Jun 23, 2016 at 09:09:44AM -0700, Walter A. Boring IV wrote: > > volumes connected to QEMU instances eventually become directly connected? > > > Our long term goal is that 100% of all network storage will be connected > > to directly by QEMU. We already have the ability to partially do

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

Le 23/06/2016 à 23:04, Thomas Goirand a écrit : Just think about it for a while. If we get Nova to work with Py3, and everything else is working, including all functional tests in Tempest, Hum, that's a long list of expectations :-) then after Otaca, we could even start to *REMOVE* Py2

Re: [openstack-dev] [all] what do you work on upstream of OpenStack?

Thanks for that Clint! On Jun 24, 2016 1:28 AM, "Clint Byrum" wrote: > Excerpts from Doug Hellmann's message of 2016-06-23 08:37:04 -0400: > > Excerpts from Doug Hellmann's message of 2016-06-13 15:11:17 -0400: > > > I'm trying to pull together some information about

Re: [openstack-dev] [all] Status of the OpenStack port to Python 3

Le 23/06/2016 à 18:11, Doug Hellmann a écrit : I'd like for the community to set a goal for Ocata to have Python 3 functional tests running for all projects. We can already experiment functional tests right now ;-) I expect to get many small issues in all projects, but it may take time to fix

[openstack-dev] Guidance to start contribution

Hi, I am Aaska Shah, a third year undergrad student at DAIICT, India. I know Python, Java, C , SQL, Php, javscript, html, css and have experience in Android and Web development. I am currently doing an internship in Robocop Technologies. Robocop help companies develop, deploy, maintain and

Re: [openstack-dev] [requirements][packaging] Normalizing requirements file

On Fri, Jun 24, 2016 at 08:44:25AM +0200, Haïkel wrote: > Roger. Who's Roger? > Maybe we can put it at the agenda to the next (or later) meeting to > work on specifications > and define the next steps before moving on. Yup sounds like a good plan. LIke I said it's a pause not a complete

Re: [openstack-dev] [requirements][packaging] Normalizing requirements file

2016-06-24 4:02 GMT+02:00 Tony Breeds : > > I think we need to pause on these 'normalizing' changes in g-r. They're > genertaing whitspace only reviews in many, (possibly all) projects that have > managed requirements. > > We need to do more testing and possibly make the

Re: [openstack-dev] [grenade] upgrades vs rootwrap

On Fri, 24 Jun 2016 at 00:40 Sean Dague wrote: > On 06/23/2016 10:07 AM, Sean McGinnis wrote: > > On Thu, Jun 23, 2016 at 12:19:34AM +, Angus Lees wrote: > >> So how does rootwrap fit into the "theory of upgrade"? > >> > >> The doc talks about deprecating config, but is