Re: [openstack-dev] [Ceilometer] "Infinite" values for "sum" and "average" fields in statistics query

Hi I am using MongoDB backend. Thanks Srikanth -Original Message- From: gord chung [mailto:[email protected]] Sent: Tuesday, October 20, 2015 9:20 AM To: [email protected] Subject: Re: [openstack-dev] [Ceilometer] "Infinite" values for "sum" and "average" fields in statistic

Re: [openstack-dev] [infra][all] Reviews with a prio label?

On Tue, Oct 20, 2015 at 06:09:51PM +0200, Markus Zoeller wrote: > In ML post [1] I wondered if it would be possible to introduce a new > "prio" label in Gerrit which could help in focusing review efforts to > increase the throughput. With this new post I'd like to discuss if we > think this could b

Re: [openstack-dev] [Fuel][Plugins][Ironic] Deploy Ironic with fuel ?

Hi Loic, the story of this plugin is a bit complicated. We've done it as PoC of integrating Ironic into Mirantis OpenStack/Fuel during 7.0 release. Currently we are working on integrating Ironic into core of Fuel targeting its 8.0 release. Given that, the plugin is not official in any sense, is no

Re: [openstack-dev] [infra][all] Reviews with a prio label?

"Daniel P. Berrange" wrote on 10/20/2015 06:21:05 PM: > From: "Daniel P. Berrange" > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 10/20/2015 06:21 PM > Subject: Re: [openstack-dev] [infra][all] Reviews with a prio label? > What you're describing is really just

Re: [openstack-dev] [infra][all] Reviews with a prio label?

This is actually something I've thought a lot about (focusing the community's review efforts), and have experimented with various solutions in the keystone community. I've built external solutions that have worked fairly well, but my current preference is to take advantage of what's already built i

Re: [openstack-dev] [infra][all] Reviews with a prio label?

On Tue, Oct 20, 2015 at 11:43 AM, Dolph Mathews wrote: > This is actually something I've thought a lot about (focusing the > community's review efforts), and have experimented with various solutions > in the keystone community. I've built external solutions that have worked > fairly well, but my

Re: [openstack-dev] [All][Glance] Feedback on the proposed refactor to the image import process required

Hello, I've updated the image import spec [4] to incorporate the discussion thus far. The fishbowl session [5] is scheduled for Thursday, October 29, 2:40pm-3:20pm. If you read through the spec and the current discussion on the review, you'll be in a good position to help us get this worked out

Re: [openstack-dev] [infra][all] Reviews with a prio label?

On 10/20/2015 12:43 PM, Dolph Mathews wrote: > This is actually something I've thought a lot about (focusing the > community's review efforts), and have experimented with various > solutions in the keystone community. I've built external solutions that > have worked fairly well, but my current pref

Re: [openstack-dev] [infra][all] Reviews with a prio label?

On Tue, Oct 20, 2015 at 12:09 PM, Sean Dague wrote: > On 10/20/2015 12:43 PM, Dolph Mathews wrote: > > This is actually something I've thought a lot about (focusing the > > community's review efforts), and have experimented with various > > solutions in the keystone community. I've built external

Re: [openstack-dev] [all][heat] Which repo to use in docs -- git.openstack.org or github.com?

On Tue, Oct 20, 2015 at 3:43 AM, Andreas Jaeger wrote: > On 2015-10-20 12:17, Qiming Teng wrote: >> >> Hi, >> >> Just encountered this again in code review [1]. The question is about >> the repository to point to when documenting things up. Between the >> following links, which one should we use?

Re: [openstack-dev] [stable] Need group membership change for manila-stable-maint

On 10/20/2015 11:19 AM, Matthew Treinish wrote: On Tue, Oct 20, 2015 at 11:16:38AM -0400, Doug Hellmann wrote: Ah, right, I always forget those are a special case, thanks. So, what *is* the process, for adding someone to the stable maintenance team? :-) https://wiki.openstack.org/wiki/Stabl

Re: [openstack-dev] [rally] Rally boot tests fails with Error Forbidden: It is not allowed to create an interface on external networks

Hi Yair, The rally version I am using is 0.1.2 > rally --version 0.1.2 Also the task file is as shown below. Do you have an example of the "network" context to skip creation on the interface on the xternal network? vagrant@rally:~/rally$ more /vagrant/boot.json {% set flavor_name = flavor_name

Re: [openstack-dev] [infra][all] Reviews with a prio label?

Upstream Gerrit has been working on a tagging feature for a while now. Take a look at the gerrit discussion thread[1] if you want more info on how it came about. They decided to call it 'hashtag' or '#' (the name being very controversial).Looks like some of the feature is in Gerrit 2.11 alrea

[openstack-dev] [cinder] Specifications to support High Availability Active-Active configurations in Cinder

Hi, We finally have ready for review all specifications required to support High Availability Active/Active configurations in Cinder's Volume nodes. There is a Blueprint to track this effort [1] and the specs are as follow: - General description of the issues and solutions [2] - Removal of Races

Re: [openstack-dev] [all][heat] Which repo to use in docs -- git.openstack.org or github.com?

On Tue, Oct 20, 2015 at 12:20 PM, Christopher Aedo wrote: > On Tue, Oct 20, 2015 at 3:43 AM, Andreas Jaeger wrote: > > On 2015-10-20 12:17, Qiming Teng wrote: > >> > >> Hi, > >> > >> Just encountered this again in code review [1]. The question is about > >> the repository to point to when docume

Re: [openstack-dev] [all][heat] Which repo to use in docs -- git.openstack.org or github.com?

On 2015-10-20 13:20:34 -0500 (-0500), Dolph Mathews wrote: [...] > +1 I would never direct anyone new straight to git.openstack.org because it > makes a poor first impression relative to github.com. I assume that's the > reason why we keep github.com as a mirror at all (?). Directing someone to a

[openstack-dev] [NFV][Telco] Meeting canceled

Hi all, No Telco Working Group meeting Wednesday October 20th due to proximity to the F2F in Tokyo and the lack of items to discuss. See you all next Tuesday! Thanks, Steve __ OpenStack Development Mailing List (not for us

Re: [openstack-dev] [NFV][Telco] Meeting canceled

- Original Message - > From: "Steve Gordon" > To: "OpenStack Development Mailing List (not for usage questions)" > , > > Hi all, > > No Telco Working Group meeting Wednesday October 20th due to proximity to the Obviously I meant 21st, apologies! -Steve > F2F in Tokyo and the lack of

Re: [openstack-dev] [rally] Rally boot tests fails with Error Forbidden: It is not allowed to create an interface on external networks

On Tue, Oct 20, 2015 at 8:39 PM, Behzad Dastur wrote: > Hi Yair, > The rally version I am using is 0.1.2 > > > rally --version > 0.1.2 > > Also the task file is as shown below. Do you have an example of the > "network" context to skip creation on the interface on the xternal network? > have you s

Re: [openstack-dev] [all][heat] Which repo to use in docs -- git.openstack.org or github.com?

On 10/21/2015 04:20 AM, Christopher Aedo wrote: On the other hand, the fact that github renders the README nicely (including images) leads to a much more inviting first impression. I think it's nice to just have a standard docs target, even if it just includes the README; [1] is an example. Th

Re: [openstack-dev] Cross-project meeting, Tue Oct 20th, 21:00 UTC

Agenda is empty, meeting is canceled. Next week's meeting is also canceled because of OpenStack Summit. I hope you'll have a safe trip to Tokyo, see you there, On 10/19/2015 08:41 AM, Emilien Macchi wrote: > Dear PTLs, cross-project liaisons, and interested team members, > > We'll have a cross-p

[openstack-dev] [Neutron] Gerrit permissions and Merge rights

Hi folks, During revision of the Neutron teams [1], we made clear that the neutron-specs repo is to be targeted by specs for all the Neutron projects (core + *-aas). For this reason I made sure that the neutron-specs-core team +2 right was extended to all the core teams. Be mindful, use your +2

Re: [openstack-dev] [Heat] core team nomination

+1 On 21/10/15 02:38, Sergey Kraynev wrote: I'd like to propose new candidates for heat core-team: Rabi Mishra Peter Razumovsky According statistic both candidate made a big effort in Heat as reviewers and as contributors [1][2]. They were involved in Heat community work during last several re

Re: [openstack-dev] [Ceilometer] "Infinite" values for "sum" and "average" fields in statistics query

could you open a bug on https://bugs.launchpad.net/ceilometer/+bugs?orderby=-id&start=0 and reference this thread i would also check to see if ceilometer-api logs have any noticeable warning/errors. it's possible a datatype is being restricted there as well. thanks On 20/10/2015 12:22 PM, S

Re: [openstack-dev] [Heat] core team nomination

+1 to both On Tue, 20 Oct 2015 11:42 pm Sergey Kraynev wrote: I'd like to propose new candidates for heat core-team: Rabi Mishra Peter Razumovsky According statistic both candidate made a big effort in Heat as reviewers and as contributors [1][2]. They were involved in Heat community work d

Re: [openstack-dev] [Heat] core team nomination

+1! From: Sergey Kraynev Sent: Tuesday, October 20, 2015 8:38 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [Heat] core team nomination I'd like to propose new candidates for heat core-team: Rabi Mishra Peter

Re: [openstack-dev] [Ceilometer] "Infinite" values for "sum" and "average" fields in statistics query

I have raised the bug for this (https://bugs.launchpad.net/ceilometer/+bug/1508220) I have checked the ceilometer-api logs when I ran the query and have not found any errors or warnings. I could see only the below two logs: 2015-10-20 17:47:06.771 84151 DEBUG ceilometer.api.controllers.v2.meter

Re: [openstack-dev] [kolla] Liberty release builds

On 10/20/15, 9:06 AM, "Paul Bourke" wrote: >Kolla core team, > >Here's a link to an etherpad created just now for deciding the process >on getting release builds to dockerhub: > >https://etherpad.openstack.org/p/kolla-release-builds > >Please review and revise. Steve, can you follow up to this

Re: [openstack-dev] [Fuel][QA][Plugins] Move functional tests from fuel-qa to the plugins

Simon, I believe that it's a mistake in fuel-qa. Valid structure is in fuel-web. Please fix the one in fuel-qa. I'm also looking forward for automated adding of people to review requests based on this file. Here is the task to track it: https://bugs.launchpad.net/fuel/+bug/1497655 On Tue, Oct 20,

[openstack-dev] [nova] python-novaclient 2.32.0 not working with rackspace

Hi everyone, We have an issue [1] in python-novaclient 2.32.0 where it's not working with rackspace cloud. It's caused by a commit [2] that changed the default requested compute API version from "latest" to "client supported latest", a specific version. We have some logic in the discover_versi

Re: [openstack-dev] [Ironic] OpenStack Ironic dinner

Did we come to a decision on what day for the Ironic dinner? On Mon, Oct 12, 2015 at 11:07 AM, Lucas Alvares Gomes wrote: > Since many of us is going to be in Tokyo for the summit, who's interested > in an OpenStack Ironic dinner? > > Let's first decide what day of the week suits most people, so

[openstack-dev] [release][ironic] Announcing Ironic 4.2.1

Hi all, We're excited to announce the release of Ironic 4.2.1. This is a patch release in the OpenStack Liberty series. This release imports Japanese translations as our first translated language, and also fixes some bugs around running on systems with the Japanese locale. Release notes can be f

Re: [openstack-dev] [Ironic] OpenStack Ironic dinner

BadCub and I have been working to find a venue that can host that many people, and haven't had any luck at all. :( I think we'll need to skip a formal team dinner this time, sorry folks. I'd still love to do something informal on Thursday night with some of you - we can work it out next week. //

Re: [openstack-dev] [ironic] [horizon] ironic panels

On Tue, Oct 20, 2015 at 04:50:04PM +0100, Beth Elwell wrote: > Hi Jim, > > I have replied inline to your comments below: > > On 19/10/2015 19:38, Jim Rollenhagen wrote: > >On Mon, Oct 19, 2015 at 07:05:04PM +0100, Beth Elwell wrote: > >>Hi all, > >> > >>I am currently in the process of writing an

[openstack-dev] 答复: [Heat] core team nomination

+1 -邮件原件- 发件人: Sergey Kraynev [mailto:[email protected]] 发送时间: 2015年10月20日 21:38 收件人: OpenStack Development Mailing List (not for usage questions) 主题: [openstack-dev] [Heat] core team nomination I'd like to propose new candidates for heat core-team: Rabi Mishra Peter Razumovsky Acco

Re: [openstack-dev] [Magnum] Coe components status

hi Vikas, thanks for propose this changes, I wonder if you can show some examples for other coes we currently supported: swarm, mesos ? if we propose a public api like you proposed, we'd better to support all coes instead of coe specific. thanks Eli. On 2015年10月20日 18:14, Vikas Choudhary wr

[openstack-dev] Custom Nova scheduler based on CPU queue length

​Hi All, I am fairly new to the OpenStack community and is trying to create a custom scheduler for Nova. A scheduler based on CPU queue length. Kindly apologize if there are any inaccuracies in my statements. As I understand a weigher for the filter scheduler that weighs filtered host machines ba

[openstack-dev] [Openstack]Devstack error tgt process related to iscsi not getting started

Hi, On running stack.sh, I am getting the below error related to tgt process, which has something to do with Cinder. 2015-10-20 23:28:24.030 | + echo_summary 'Starting Cinder' 2015-10-20 23:28:24.030 | + [[ -t 3 ]] 2015-10-20 23:28:24.030 | + [[ True != \T\r\u\e ]] 2015-10-20 23:28:24.030 | + ech

Re: [openstack-dev] [nova] python-novaclient 2.32.0 not working with rackspace

Looks like we use API_MAX_VERSION and DEFAULT_OS_COMPUTE_API_VERSION with wrong way. This isn't broken with rackspace only, this broken novaclient runing with nova legacy v2 api(legacy v2 api's behavior is no version exposed). API_MAX_VERSION is the max version of client supported, currently it sh

Re: [openstack-dev] [nova] python-novaclient 2.32.0 not working with rackspace

I just work out a patch quickly for fixing this, https://review.openstack.org/237850 2015-10-21 10:08 GMT+08:00 Alex Xu : > Looks like we use API_MAX_VERSION and DEFAULT_OS_COMPUTE_API_VERSION with > wrong way. This isn't broken with rackspace only, this broken novaclient > runing with nova legac

Re: [openstack-dev] [Neutron] Do not merge until further notice

i missed the "further notice"? On Wed, Oct 14, 2015 at 4:07 AM, Armando M. wrote: > Hi folks, > > We are in the last hours of Liberty, let's pause for a second and consider > merging patches only if absolutely necessary. The gate is getting clogged > and we need to give priority to potential RC3

[openstack-dev] [Neutron] HenryG addition to the Neutron Drivers team

Hi folks, Henry has been instrumental in many areas of the projects and his crazy working hours makes even Kevin and I bow in awe. Jokes aside, I would like to announce HenryG as a new member of the Neutron Drivers team. Having a propension to attendance, and desire to review of RFEs puts you on

Re: [openstack-dev] [Magnum] Coe components status

@ Eli , I will look into how to support this feature for other COEs also(mesos and swarm). But anyways Magnum's goal is to provide users *atleast* what other coes are providing (if not something extra). All coes dont have common features, so we cant be very strict on providing common interface api

Re: [openstack-dev] [Magnum] Coe components status

+ 1 to vikas. As we have monitor framework only to docker swarm COE at present and we are pushing other COE drivers in future. So it is better to have component status for one COE at first and will push other COEs support later. Correct me if I am wrong. Regards Bharath T On Wed, Oct 21, 2015 at

[openstack-dev] [neutron][fwaas] openstack summit meetup

Hi, Will there be a meetup or design session for FWaaS? I just saw the roadmap presentation at the main conf. -- Oğuz Yarımtepe http://about.me/oguzy __ OpenStack Development Mailing List (not for usage questions) Unsubscrib

Re: [openstack-dev] [nova-compute][nova][libvirt] Extending Nova-Compute for image prefetching

Hi, Alberto, I'm really interested in your proposal, have you already submitted your spec? or is there any topic for you to have a discussion with Nova team in design summit? I wonder what if the nova compute host use shared storage backend, like NFS or Ceph? I have another suggestion, we can co

[openstack-dev] The OVS and Provider Networks section of the guide to Neutron in DevStack

First let me make sure I understand what this section ( http://docs.openstack.org/developer/devstack/guides/neutron.html#neutron-networking-with-open-vswitch-and-provider-networks ) is trying to say. The second paragraph is saying that some infrastructure provider has allocated a VLAN tag (and th

Re: [openstack-dev] [neutron][fwaas] openstack summit meetup

There are two slots (combined with LBaaS) Thu, Oct 29, 11am and the follow on at 11:50am [1]. Thanks Sridar [1] http://mitakadesignsummit.sched.org/overview/type/neutron From: Oğuz Yarımtepe mailto:[email protected]>> Reply-To: OpenStack List mailto:[email protected]>>

Re: [openstack-dev] [Neutron] Do not merge until further notice

On 20 October 2015 at 19:46, Takashi Yamamoto wrote: > i missed the "further notice"? > No, you didn't. RC3 released, Liberty released, the world moved on and I didn't think of sending an email. Sorry. > > On Wed, Oct 14, 2015 at 4:07 AM, Armando M. wrote: > > Hi folks, > > > > We are in the

Re: [openstack-dev] [Neutron] HenryG addition to the Neutron Drivers team

Excellent addition! Remember everyone, if the feature you want doesn't make it into Neutron, it's now Henry's fault. :) On Tue, Oct 20, 2015 at 8:14 PM, Armando M. wrote: > Hi folks, > > Henry has been instrumental in many areas of the projects and his crazy > working hours makes even Kevin and

Re: [openstack-dev] [Fuel][QA][Plugins] Move functional tests from fuel-qa to the plugins

Simon, structure of fuel-web repo is much more complex than fuel-qa, ~ 50 active contributors work with fuel-web. There is the functionality of the different Fuel domains and each requires its own expertise, so maintenance is divided by folders. In case of fuel-qa maintainers are doing review for w

Re: [openstack-dev] [Fuel] Modularization activity POC

Thanks Eugene. I'd recommend to start integration as early as possible... On Tue, Oct 20, 2015 at 2:11 AM Evgeniy L wrote: > Hi Mike, > > 1. our plan is to have working partitioning/provisioning in a couple of > weeks, > networking is more complicated and it's better to ask Vladimir/Ryan. >

Re: [openstack-dev] [Fuel][Plugins] Plugin deployment questions

Hi all, is there a plan to remove this restriction permanently? Any bug/blueprint covering it? On Tue, Oct 20, 2015 at 5:07 AM Patrick Petit wrote: > Hi Matthew, > > That’s useful. > Thanks > > On 20 Oct 2015 at 11:22:07, Matthew Mosesohn ([email protected]) > wrote: > > Hi Patrick, > > Dur

Re: [openstack-dev] [Fuel][QA][Plugins] Move functional tests from fuel-qa to the plugins

Nastya, according to the template I provided initially [1] format in fuel-qa is invalid. I've requested to support only one format [2]. File must always have a folder. If you want to cover the whole repo, then the right structure would be maintainers: - ./: - name: ... email: ...

Re: [openstack-dev] [all][heat] Which repo to use in docs -- git.openstack.org or github.com?

On 20/10/15 18:34 +, Jeremy Stanley wrote: On 2015-10-20 13:20:34 -0500 (-0500), Dolph Mathews wrote: [...] +1 I would never direct anyone new straight to git.openstack.org because it makes a poor first impression relative to github.com. I assume that's the reason why we keep github.com as a

Re: [openstack-dev] [mistral] How to call 3rd-party tools(such as Ansible) in Mistral

> On 20 Oct 2015, at 14:58, WANG, Ming Hao (Tony T) > wrote: > > Another question is: > If I use custom action to run Ansible, the Ansible playbook should be stored > on the same server of Mistral. Is it right? Depends on how this action is implemented (it can, for example, do ssh to other s

Re: [openstack-dev] [Fuel][QA][Plugins] Move functional tests from fuel-qa to the plugins

2015-10-21 8:11 GMT+02:00 Mike Scherbakov : > > Simon is asking a valid request: if you add his folder in the file, he > will be always added to the review request by script, once it's > implemented. Only in the case when contribution is made to his particular > area of responsibility. > Mike, wh

Re: [openstack-dev] [mistral] How to call 3rd-party tools(such as Ansible) in Mistral

> On 19 Oct 2015, at 13:18, WANG, Ming Hao (Tony T) > wrote: > > I like your > option2(https://blueprints.launchpad.net/mistral/+spec/action-providers > ). J > Any schedule for this? Looks like it isn’t started yet. No particul

Re: [openstack-dev] [Heat] core team nomination

+1 to both. Qiming On Tue, Oct 20, 2015 at 04:38:12PM +0300, Sergey Kraynev wrote: > I'd like to propose new candidates for heat core-team: > Rabi Mishra > Peter Razumovsky > > According statistic both candidate made a big effort in Heat as > reviewers and as contributors [1][2]. > They were inv

Re: [openstack-dev] [Fuel][Plugins][Ironic] Deploy Ironic with fuel ?

+ Pavlo, Andrey. Aleksey Kasatkin On Mon, Oct 19, 2015 at 6:45 AM, wrote: > Hello, > > > > I’m currently searching for information about Ironic Fuel plugin : > https://github.com/openstack/fuel-plugin-ironic I don’t find any > documentation on it. > > > > I’ve tried to install and deploy an O

[openstack-dev] [neutron][client] collecting opinions on neutronclient options

Hi team, Recently there are many patches to add help messages to neutron *-update sub-commands (or others). I made similar comments and discussions repeatedly in various reviews. I created a etherpad page [1] to dicsuss neutronclient options Once we collect opinions and have a consensus, I will

Re: [openstack-dev] [mistral] How to call 3rd-party tools(such as Ansible) in Mistral

Renat, Another question is: If I use custom action to run Ansible, the Ansible playbook should be stored on the same server of Mistral. Is it right? Thanks, Tony From: Renat Akhmerov [mailto:[email protected]] Sent: Monday, October 19, 2015 2:58 PM To: OpenStack Development Mailing List (n

Re: [openstack-dev] [Fuel][QA][Plugins] Move functional tests from fuel-qa to the plugins

Thanks for the reply, Andrew! I must admit that I haven't read thoroughly the specification on the new team structure [1]. IIUC plugin developers should be added to the MAINTAINERS file of fuel-qa for the directories that concern their plugins. If I take LMA as an example, this would be: fuelweb_te

Re: [openstack-dev] [Fuel] Modularization activity POC

Hi Mike, 1. our plan is to have working partitioning/provisioning in a couple of weeks, networking is more complicated and it's better to ask Vladimir/Ryan. 2, 3. here we have just some general ideas, we should have independent releases on pypi, each component should have responsible perso

Re: [openstack-dev] [Fuel][Plugins] Plugin deployment questions

Hi Patrick, During the 7.0 development cycle we made a lot of enhancements to what environment characteristics can be modified through a plugin. One item that plugins cannot directly modify is the default Fuel roles and their metadata. That having been said, there is an open-ended post_install.sh

Re: [openstack-dev] [Fuel] Assigning VIPs on network config serialization

My concern here is that there is also a Network check feature that according to its name should check things like whether or not there’s enough IP addresses in all ranges in a network. The problem is that it may be run at any time, even when VIPs are not yet allocated. From a user-side the workf

Re: [openstack-dev] [mistral] How to call 3rd-party tools(such as Ansible) in Mistral

Hi, Minghao, The answer is yes, if you want to use Ansible playbook in you customized 'ansible actions', you need put the playbooks under a place that your code has access to. BTW, you can send personal email to me in Chinese, in case you want to solve your problems quickly :-) On Tue, Oct 20, 2

Re: [openstack-dev] [mistral] How to call 3rd-party tools(such as Ansible) in Mistral

Or, feel free to join our IRC channel for quick response, #openstack-mistral On Tue, Oct 20, 2015 at 4:58 PM, WANG, Ming Hao (Tony T) wrote: > Renat, > > > > Another question is: > > If I use custom action to run Ansible, the Ansible playbook should be stored > on the same server of Mistral. Is i

[openstack-dev] [Magnum] Coe components status

Hi Team, I would appreciate any opinion/concern regarding "coe-component-status" feature implementation [1]. For example in k8s, using API api/v1/namespaces/{namespace}/componentstatuses, status of each k8s component can be queried. My approach would be to provide a command in magnum like "magnum

[openstack-dev] [all][heat] Which repo to use in docs -- git.openstack.org or github.com?

Hi, Just encountered this again in code review [1]. The question is about the repository to point to when documenting things up. Between the following links, which one should we use? - https://git.openstack.org/cgit/openstack/sqlalchemy-migrate - https://github.com/openstack/sqlalchemy-migrate I

Re: [openstack-dev] [Fuel] Testing before switching to upstream librarian

Ivan, BVT is not source of truth. BVT handles couple of scenarios from hundreds. You should rely on swarm test and get parity in % of failed tests. -- Best regards, Sergii Golovatiuk, Skype #golserge IRC #holser On Mon, Oct 19, 2015 at 9:10 PM, Ivan Berezovskiy wrote: > Hi, > > First of all, I

Re: [openstack-dev] [Fuel][Fuel-Modularization] Proposal on Decoupling Serializers from Nailgun

Hi, I have a comment regarding to when/where run translators. I think data processing (fetching + validation + translation) should be done as a separate stage, this way when we start deployment, we are sure that we have everything we need to perform deployment, but I understand that there might be

Re: [openstack-dev] [Fuel] Testing before switching to upstream librarian

Hi, On Mon, Oct 19, 2015 at 10:46 PM, Sergey Kolekonov wrote: > Hi, > > I agree with Ivan. Getting rid of forks and moving to puppet-librarian is > complicated work and such problems are nearly unavoidable. It's hard to > cover all possible corner cases with regular tests. > This case shows the

Re: [openstack-dev] [all][heat] Which repo to use in docs -- git.openstack.org or github.com?

On 2015-10-20 12:17, Qiming Teng wrote: Hi, Just encountered this again in code review [1]. The question is about the repository to point to when documenting things up. Between the following links, which one should we use? - https://git.openstack.org/cgit/openstack/sqlalchemy-migrate - https://

Re: [openstack-dev] [Fuel] Testing before switching to upstream librarian

Folks This is what we should discuss. Let's think of better testing coverage when we decide to switch to new tag. We MUST NOT skip a single bug which we fixed in downstream. So this means that for each bug fixed in downstream there should be a set of tests merged into our testing framework along w

Re: [openstack-dev] [Neutron] [Tempest] where fwaas tempest tests should be?

My only concern is how tightly coupled the FwaaS code is with the L3 agent. We have a bug already filed because the L3 agent inheriting the FwaaS code causes circular dependencies, but it also be the reason why FwaaS co-gates with the main Neutron repo. Let's try and fix the tight coupling of t

[openstack-dev] [rally] Rally boot tests fails with Error Forbidden: It is not allowed to create an interface on external networks

I have a contrail/OpenStack cloud deployed on which I am trying to run some rally benchmarks. But I am having trouble getting the rally boot tests to run. It throws the "Error Forbidden: It is not allowed to create an interface on external network" It seems it is trying to create an interface on t

Re: [openstack-dev] [Fuel][Fuel-Modularization] Proposal on Decoupling Serializers from Nailgun

Folks Can we please stop using etherpad and move to some more usable thing as Google Docs? Etherpad seems too unusable for such discussion especially with this coloured formatting. Mike I currently see no need in following marketing trend for noSQL here - we need to store a set of structured dat

[openstack-dev] [puppet] Match type checking from oslo.config.

Hi, The idea would be to have some of the types defined oslo config http://git.openstack.org/cgit/openstack/oslo.config/tree/oslo_config/types.py ported to puppet type. Those that looks like good candidates are: - Boolean; - IPAddress; and in a lesser extend: - Integer; - Float; For instance

[openstack-dev] [all] jobs that will fail when extras.d support in Devstack is removed in 8 weeks

Logstash has been upgraded, so the old urls won't work any more. However here are the top 9 jobs from yesterday that will fail after this change: gate-murano-congress-devstack-dsvm gate-murano-devstack-dsvm gate-rally-dsvm-murano-task gate-designate-dsvm-powerdns gate-solum-devstack-dsvm gate-rall

Re: [openstack-dev] [Fuel][Plugins] Plugin deployment questions

Hi Matthew, That’s useful. Thanks On 20 Oct 2015 at 11:22:07, Matthew Mosesohn ([email protected]) wrote: Hi Patrick, During the 7.0 development cycle we made a lot of enhancements to what environment characteristics can be modified through a plugin. One item that plugins cannot directly

Re: [openstack-dev] [rally] Rally boot tests fails with Error Forbidden: It is not allowed to create an interface on external networks

On Tue, Oct 20, 2015 at 2:06 PM, Behzad Dastur wrote: > I have a contrail/OpenStack cloud deployed on which I am trying to run > some rally benchmarks. But I am having trouble getting the rally boot tests > to run. It throws the "Error Forbidden: It is not allowed to create an > interface on exte

Re: [openstack-dev] [puppet] Running Debian packages on top of Trusty

Thomas Goirand writes: > On 10/07/2015 12:22 PM, Sofer Athlan-Guyot wrote: >> Hi, >> >> On 2 Oct 2015, [email protected] wrote: >> >>> Hello, >>> >>> thanks for bringing up this topic, that's what I wanted to discuss on >>> next puppet-openstack irc meeting. >>> >>> So, user case is fol

Re: [openstack-dev] [all][heat] Which repo to use in docs -- git.openstack.org or github.com?

On 10/20/2015 06:43 AM, Andreas Jaeger wrote: On 2015-10-20 12:17, Qiming Teng wrote: Hi, Just encountered this again in code review [1]. The question is about the repository to point to when documenting things up. Between the following links, which one should we use? - https://git.openstack.o

Re: [openstack-dev] [infra] Upgrade to Gerrit 2.11

Markus Zoeller said on Fri, Oct 16, 2015 at 03:33:37PM +0200: > > >Would it be possible to create a "prio" label to help sorting out > stuff? +1 to this! > > I guess topics could be used but those are overwritten on every new > > PS. > > The topics survive a new patch set, as far as I observed

Re: [openstack-dev] [all][heat] Which repo to use in docs -- git.openstack.org or github.com?

On 20 October 2015 at 16:04, Monty Taylor wrote: > On 10/20/2015 06:43 AM, Andreas Jaeger wrote: >> >> On 2015-10-20 12:17, Qiming Teng wrote: >>> >>> Hi, >>> >>> Just encountered this again in code review [1]. The question is about >>> the repository to point to when documenting things up. Betwee

Re: [openstack-dev] [stable] Need group membership change for manila-stable-maint

Excerpts from Ben Swartzlander's message of 2015-10-19 21:02:46 -0400: > I would like the manila-core group added as an included group in > manila-stable-maint. I'm not sure what the right procedure is so I'm > asking here. > > -Ben Swartzlander > Most gerrit groups are self-service by the mem

[openstack-dev] [Heat] core team nomination

I'd like to propose new candidates for heat core-team: Rabi Mishra Peter Razumovsky According statistic both candidate made a big effort in Heat as reviewers and as contributors [1][2]. They were involved in Heat community work during last several releases and showed good understanding of Heat co

Re: [openstack-dev] [stable] Need group membership change for manila-stable-maint

On 2015-10-20 09:31:52 -0400 (-0400), Doug Hellmann wrote: > Excerpts from Ben Swartzlander's message of 2015-10-19 21:02:46 -0400: > > I would like the manila-core group added as an included group in > > manila-stable-maint. I'm not sure what the right procedure is so I'm > > asking here. [...]

Re: [openstack-dev] [Fuel] Assigning VIPs on network config serialization

Andrew, > but the problem lies that VIP's need to already be allocated. Why? Fuel doesn't use them on this stage. > They need to be allocated on network update, or when a node role requiring > one is added to the environment. It looks like either you or me misunderstood something. AFAIK, node

Re: [openstack-dev] [Fuel] Assigning VIPs on network config serialization

Roman, > This behavior is actually described in [1]. Should we allocate > VIPs on network check as well? No, we shouldn't. We should check whether it's enough IPs for nodes / VIPs with current network configuration, but no more. - igor On Tue, Oct 20, 2015 at 4:54 PM, Igor Kalnitsky wrote: > A

Re: [openstack-dev] [Heat] core team nomination

+1 Original message From: Sergey Kraynev Date:10/20/2015 8:42 AM (GMT-06:00) To: "OpenStack Development Mailing List (not for usage questions)" Subject: [openstack-dev] [Heat] core team nomination I'd like to propose new candidates for heat core-team: Rabi Mishra Peter Razumovsk

Re: [openstack-dev] [puppet][Fuel] Using Native Ruby Client for Openstack Providers

Gilles Dubreuil writes: > On 14/10/15 17:15, Gilles Dubreuil wrote: >> >> >> On 14/10/15 10:36, Colleen Murphy wrote: >>> >>> >>> On Tue, Oct 13, 2015 at 6:13 AM, Vladimir Kuklin >> > wrote: >>> >>> Puppetmaster and Fuelers, >>> >>> Last week I mentioned tha

Re: [openstack-dev] [Heat] core team nomination

+1 to both Rabi Mishra & Peter Razumovsky. -Kanagaraj M -Original Message- From: Sergey Kraynev [mailto:[email protected]] Sent: Tuesday, October 20, 2015 7:08 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [Heat] core team nomination

[openstack-dev] [kolla][announce] Kolla Liberty Release Announcement

Hello OpenStackers! The Kolla community is pleased to announce the release of the Kolla Liberty. This release fixes 432 bugs and implements 58 blueprints! During Liberty, Kolla joined the big tent governance! Our project can be found here: http://governance.openstack.org/reference/project

[openstack-dev] [Fuel] fuelmenu code freeze

Dear colleagues, As you might know I'm working on splitting multiproject fuel-web repository into several sub-projects. Fuelmenu is one of directories that are to be moved to a separate git project. Checklist for this to happen is as follows: - Launchpad bug: https://bugs.launchpad.net/fuel/+

Re: [openstack-dev] [Heat] core team nomination

On Tue, Oct 20, 2015 at 04:38:12PM +0300, Sergey Kraynev wrote: > I'd like to propose new candidates for heat core-team: > Rabi Mishra > Peter Razumovsky > > According statistic both candidate made a big effort in Heat as > reviewers and as contributors [1][2]. > They were involved in Heat communi

Re: [openstack-dev] [Heat] core team nomination

+1! -- Thomas On Tue, Oct 20, 2015 at 3:38 PM, Sergey Kraynev wrote: > I'd like to propose new candidates for heat core-team: > Rabi Mishra > Peter Razumovsky > > According statistic both candidate made a big effort in Heat as > reviewers and as contributors [1][2]. > They were involved in Hea

Re: [openstack-dev] [stable] Need group membership change for manila-stable-maint

Excerpts from Jeremy Stanley's message of 2015-10-20 13:41:05 +: > On 2015-10-20 09:31:52 -0400 (-0400), Doug Hellmann wrote: > > Excerpts from Ben Swartzlander's message of 2015-10-19 21:02:46 -0400: > > > I would like the manila-core group added as an included group in > > > manila-stable-ma

Re: [openstack-dev] [stable] Need group membership change for manila-stable-maint

On Tue, Oct 20, 2015 at 11:16:38AM -0400, Doug Hellmann wrote: > Excerpts from Jeremy Stanley's message of 2015-10-20 13:41:05 +: > > On 2015-10-20 09:31:52 -0400 (-0400), Doug Hellmann wrote: > > > Excerpts from Ben Swartzlander's message of 2015-10-19 21:02:46 -0400: > > > > I would like the

  1   2   >