[openstack-dev] [Security] No IRC meeting this week

All, No IRC meeting this week as we're conducting the mid-cycle in Austin Weds->Friday. However, we'll be doing hangouts for those who can't make it onsite and will be monitoring IRC so just ping us on there if you want to contribute. Cheers -Rob

Re: [openstack-dev] swiftclient report that header value 120 must be of type str or bytes, not , the detail info is like the following

This is the result of a fairly recent change in requests [1], released 8 Aug. While the enforcement of header-value types is fairly recent, they've documented since 2.0.1 that headers must be byte- or unicode-strings [2], and more recently clarified it in their quick start guide [3]. It looks

Re: [openstack-dev] [kolla][osic] OSIC cluster status

Ok so I got up to speed - We were having trouble getting instances to get an IP on the VLAN provider network via DHCP. DHCP responses were being sent by the neutron dhcp agent but seemed to be getting dropped at br-ex. Turned out the kernel running in the ISO we are using is not new enough

Re: [openstack-dev] [neutron][networking-sfc] Unable to create openstack SFC

Hi Alioune, Please find me in IRC * #openstack-neutron *name:* mohankumar* Yes ,the error looks confusing , but logs at "2016-08-16 17:32:35.255 " showing networking_sfc.services.sfc.drivers.ovs.driver function called as *'ingress': None * , Hence the create port_chain at sfc driver

[openstack-dev] [tripleo] State of upgrade CLI commands

Hello TripleO-ians, I've started to look again at the introduced, but unused/undocumented upgrade commands. It seems to me that given the current state of the upgrade process (at least from Liberty -> Mitaka), these commands make a lot less sense. I see one of two directions to take on this. Of

Re: [openstack-dev] FW: [Ceilometer]:Duplicate messages with Ceilometer Kafka Publisher.

Hi Simon, I have two openstack setup's one with kilo and other with mitaka. Please find details of kafka version's below: Kilo kafka client library Version:1.3.1 Mitaka kafka client library Version:1.3.1 Kafka server version on both kilo and mitaka: kafka_2.11-0.9.0.0.tgz One observation is on

Re: [openstack-dev] [vitrage] scenario evaluator not enabled by default

Hi Yujun, I think you will find what you are looking for in “consistency_enforcer.py”. Hope it helps. Nofar Schnider Senior Software Engineer Applications & Analytics, Nokia 16 Atir Yeda Kfar Saba, Israel 44643 M: +972 52 4326023 F: +972 9 793 3036 [download] From: Yujun Zhang

Re: [openstack-dev] how to add ironic db version file. now install don't copying db version file. how to do?

Hi Paul, I want add a db version file. can tell me how to do ? very very thank you > !!! > To create a migration script you have to do: $ cd ironic/ironic/db/sqlalchemy $ alembic revision -m "create foo table" We maintain a FAQ as part of the Ironic documentation that answer this and other

Re: [openstack-dev] [neutron][networking-sfc] Unable to create openstack SFC

Hi all, You can see below the debuf logs at the creation of service chain Regards, vagrant@ubuntu:~/openstack_sfc$ neutron --debug port-chain-create --port-pair-group PG1 --port-pair-group PG2 --flow-classifier FC15 PC1 DEBUG: keystoneclient.session REQ: curl -g -i -X GET

[openstack-dev] [vitrage][vitrage-dashboard] missing icon/font in alarm list under material theme

The alarm list is not displaying some icon/font correctly under Material theme. See attached screenshots. Could anybody have a look? Tracked in https://bugs.launchpad.net/vitrage-dashboard/+bug/1613574 Material: [image: Screen Shot 2016-08-16 at 3.14.26 PM.png] × [image: Screen Shot 2016-08-16

Re: [openstack-dev] [OpenStack-docs] [Magnum] Using common tooling for API docs

Hi Anne, AFAIK, the API WG adopted Swagger (OpenAPI) as common tool for API docs. Anne, has not the adoption been changed? Otherwise, do we need to maintain much RST files also? IMO, for that the reference and the source code doesn't have conflict, these should be near each other as possible

Re: [openstack-dev] [Nova][API] Need naming suggestions for "capabilities"

Le 15/08/2016 22:59, Andrew Laski a écrit : On Mon, Aug 15, 2016, at 10:33 AM, Jay Pipes wrote: On 08/15/2016 09:27 AM, Andrew Laski wrote: Currently in Nova we're discussion adding a "capabilities" API to expose to users what actions they're allowed to take, and having compute hosts expose

Re: [openstack-dev] [Ceilometer] Newbie question regarding Ceilometer notification plugin

On Mon, Aug 15 2016, Wanjing Xu (waxu) wrote: > We are trying to develop a program which can draw the VMs topology. For > this we need to listen VM creation/deletion event and act upon it. I > would think Ceilometer is the right place for this. So I download and > read Ceilometer a little bit.

[openstack-dev] [Fuel] Getting rid of ISO

Dear colleagues, We finally have working custom deployment job that deploys Fuel admin node using online RPM repositories (not ISO) on vanilla Centos 7.0. Currently all Fuel system and deployment tests use ISO and we are planning to re-implement all these jobs (including BVT, SWARM, and Fuel CI

[openstack-dev] [tripleo] fluentd client composable service (request for review)

Howdy, I'm working on a composable service to install the fluentd client across the overcloud (and provide appropriate configuration files to pull in relevant openstack logfiles). There are two* reviews pending right now: - in tripleo-heat-templates: https://review.openstack.org/#/c/353506 - in

Re: [openstack-dev] [kuryr][kolla] keystone v3 support status and plans?

On Tue, Aug 16, 2016 at 2:56 PM, Steven Dake (stdake) wrote: > Hey kuryrians, > > Kolla has a kuryr review in our queue and its looking really solid from > Hui Kang. The last key problem blocking the merge (and support of Kuryr in > Kolla) is that Kolla only supports keystone

[openstack-dev] [Kuryr] Proposing vikasc for kuryr-libnetwork core

Hi Kuryrs, I would like to propose Vikas Choudhary for the core team for the kuryr-libnetwork subproject. Vikas has kept submitting patches and reviews at a very good rhythm in the past cycle and I believe he will help a lot to move kuryr forward. I would also like to propose him for the core

Re: [openstack-dev] [Heat][Horizon] Any guidelines for naming heat resource type names?

On 16/08/16 17:43, Praveen Yalagandula wrote: Hi all, We have developed some heat resources for our custom API server. We followed the instructions in the development guide at http://docs.openstack.org/developer/heat/pluginguide.html and got everything working. However, the Horizon "Resource

Re: [openstack-dev] [tripleo] Testing optional composable services in the CI

On Mon, Aug 15, 2016 at 4:54 AM, Dmitry Tantsur wrote: > Hi everyone, happy Monday :) > > I'd like to start the discussion about CI-testing the optional composable > services in the CI (I'm primarily interested in Ironic, but I know there are > a lot more). > > Currently

Re: [openstack-dev] [all][infra] Binary Package Dependencies - not only for Python

On Fri, Aug 12, 2016 at 2:53 PM, Jeremy Stanley wrote: > On 2016-08-12 21:20:34 +0200 (+0200), Julien Danjou wrote: > [...] > > If bindep.txt is present, are the "standard" packages still installed? > > If yes, this is going to be more challenging to get bindep.txt right, as >

[openstack-dev] [Heat][Horizon] Any guidelines for naming heat resource type names?

Hi all, We have developed some heat resources for our custom API server. We followed the instructions in the development guide at http://docs.openstack.org/developer/heat/pluginguide.html and got everything working. However, the Horizon "Resource Types" panel is returning a 500 error with

Re: [openstack-dev] [nova] os-capabilities library created

On Tue, 16 Aug 2016, Alex Xu wrote: There are two solutions in my mind 1. There aren't different dependence for traits, that is easy. The validation API in the placement engine API is enough. 2. There are different dependence for traits. We need API for compute node report those dependence.

Re: [openstack-dev] [manila] nfs-ganesha export modification issue

On Thursday, June 30, 2016 6:07 PM, Alexey Ovchinnikov wrote: > > Hello everyone, > > here I will briefly summarize an export update problem one will encounter > when using nfs-ganesha. > > While working on a driver that relies on nfs-ganesha I have discovered that

[openstack-dev] [kuryr][kolla] keystone v3 support status and plans?

Hey kuryrians, Kolla has a kuryr review in our queue and its looking really solid from Hui Kang. The last key problem blocking the merge (and support of Kuryr in Kolla) is that Kolla only supports keystone v3 (and later when that comes from upstream). As a result we are unable to merge kuryr

Re: [openstack-dev] [neutron][networking-ovs-dpdk] conntrack security group driver with ovs-dpdk

> -Original Message- > From: Assaf Muller [mailto:as...@redhat.com] > Sent: Monday, August 15, 2016 2:50 PM > To: OpenStack Development Mailing List (not for usage questions) > > Cc: Mooney, Sean K > Subject: Re:

Re: [openstack-dev] [barbican] Secure Setup & HSM-plugin

Hi Douglas, Thank you very much for your response. When testing the usage of the generated MKEK, we ran into some problems. For clarification: we are testing the PKCS#11-based crypto plugin with a Utimaco HSM. The error messages are from Barbican's and Utimaco's log files. When storing a

Re: [openstack-dev] [Ceilometer] Newbie question regarding Ceilometer notification plugin

On 15/08/16 02:23 PM, Wanjing Xu (waxu) wrote: We are trying to develop a program which can draw the VMs topology. For this we need to listen VM creation/deletion event and act upon it. I would think Ceilometer is the right place for this. So I download and read Ceilometer a little bit. If

Re: [openstack-dev] [nova][vitrage] host evacuate

On 8/16/2016 12:39 AM, Afek, Ifat (Nokia - IL) wrote: On 15/08/2016, 19:29, "Matt Riedemann" wrote: On 8/15/2016 4:24 AM, Afek, Ifat (Nokia - IL) wrote: Hi, In Vitrage project[1], I would like to add an option to call nova host-evacuate for a failed host. I

Re: [openstack-dev] [neutron][networking-sfc] Unable to create openstack SFC

Hi Alioune, Could you share neutron log as well ? also let us know your sfc code base., If possible shall we have quick chat on this in neutron IRC channel ? Thanks., Mohankumar.N On Mon, Aug 15, 2016 at 5:09 PM, Alioune wrote: > Hi all, > I'm trying to launch Openstack

Re: [openstack-dev] [vitrage] scenario evaluator not enabled by default

Found it at https://github.com/openstack/vitrage/blob/master/vitrage/entity_graph/consistency/consistency_enforcer.py#L58 Thanks, Nofar. On Tue, Aug 16, 2016 at 3:09 PM Schnider, Nofar (EXT - IL) < nofar.schnider@nokia.com> wrote: > Hi Yujun, > > I think you will find what you are looking

[openstack-dev] Neutron Bug Deputy report

Neutrinos, Since the Neutron mid-cycle has pre-empted the usual team meeting, I am issuing my report as bug deputy for the week of August 8-16 in email form. There were five critical bugs filed last week, two of which are still outstanding. They are: 1.

[openstack-dev] [Murano] Developer's productivity with MuranoPL

Hi folks, The developer's productivity and ease of use is critical for the language adoption, and I believe we have issues with these in MuranoPL. The things are slowly getting better (thanks to the guys who are bulding th MuranoPL syntax checker [1] which will be a very useful tool), but that's

[openstack-dev] [nova] The great deproxification of novaclient

The 2.36 microversion in nova's REST API makes proxy APIs for images, baremetal, volumes and network resources return a 404. http://specs.openstack.org/openstack/nova-specs/specs/newton/approved/deprecate-api-proxies.html We realized after the fact that to support 2.36 in novaclient we

Re: [openstack-dev] [all][tc][ptl] establishing project-wide goals

On 08/16/2016 05:36 AM, Thierry Carrez wrote: > John Dickinson wrote: Excerpts from John Dickinson's message of 2016-08-12 16:04:42 -0700: > [...] > The proposed plan has a lot of good in it, and I'm really happy to see > the TC > working to bring common goals and vision to

Re: [openstack-dev] [TripleO] tripleo-common bugs, bug tracking and launchpad tags

On 19 July 2016 at 16:20, Steven Hardy wrote: > On Mon, Jul 18, 2016 at 12:28:10PM +0100, Julie Pichon wrote: >> Hi, >> >> On Friday Dougal mentioned on IRC that he hadn't realised there was a >> separate project for tripleo-common bugs on Launchpad [1] and that he'd >> been

[openstack-dev] [tripleo] weekly meeting Aug 16

Hi, TripleO team did weekly meeting and you can read notes here: http://eavesdrop.openstack.org/meetings/tripleo/2016/tripleo.2016-08-16-14.00.html Thanks, -- Emilien Macchi __ OpenStack Development Mailing List (not for

[openstack-dev] [vitrage] add the resource to the alarm notification

Hi, I'm writing an alarm notifier that need to get from vitrage graph the resource along with the alarm. So I've added blueprint : https://blueprints.launchpad.net/vitrage/+spec/add-resource-to-alarm-notification I've also wrote the code that implement it. And I'm ready to commit it. BR

Re: [openstack-dev] [Nova][API] Need naming suggestions for "capabilities"

> On Aug 15, 2016, at 10:49 AM, Doug Hellmann wrote: > > Excerpts from Jim Meyer's message of 2016-08-15 09:37:36 -0700: >> A fast reply where others will expand further (I hope): >> >>> On Aug 15, 2016, at 9:01 AM, Doug Hellmann wrote: >>>

[openstack-dev] [Nova] live migration meeting today

See agenda and add if you have something to bring up: https://wiki.openstack.org/wiki/Meetings/NovaLiveMigration Paul __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [fuel] mcollective configuration on slaves

Currently we use /etc/nailgun-agent/nodiscover file to prevent early run of nailgun-agent (and thus its conflict with cloud-init). We put this file when we build an image [0] and then we remove this file at the late stage of system start process when cloud-init is done [1]. Anyway this does not

[openstack-dev] [TripleO][CI][Delorean]

Hi, all we have current tripleo repo[1] pointing to old repository[2] which contains broken cinder[3] with volumes type bug[4] That breaks all our CI jobs which can not create pingtest stack, because current-tripleo is the main repo that is used in jobs[5] Could we move the link please to any

Re: [openstack-dev] [all][tc][ptl] establishing project-wide goals

John Dickinson wrote: >>> Excerpts from John Dickinson's message of 2016-08-12 16:04:42 -0700: [...] The proposed plan has a lot of good in it, and I'm really happy to see the TC working to bring common goals and vision to the entirety of the OpenStack community. Drop the

Re: [openstack-dev] [Fuel] Getting rid of ISO

On 08/16/2016 04:58 AM, Vladimir Kozhukalov wrote: Dear colleagues, We finally have working custom deployment job that deploys Fuel admin node using online RPM repositories (not ISO) on vanilla Centos 7.0. Bravo! :) Currently all Fuel system and deployment tests use ISO and we are planning

Re: [openstack-dev] FW: [Ceilometer]:Duplicate messages with Ceilometer Kafka Publisher.

what does your pipeline.yaml look like? maybe paste it to paste.openstack.org. i imagine it's correct if your udp publishing works as expected. On 16/08/16 04:04 AM, Raghunath D wrote: Hi Simon, I have two openstack setup's one with kilo and other with mitaka. Please find details of kafka

Re: [openstack-dev] [Puppet] Puppet OpenStack Application Module

On Mon, Aug 15, 2016 at 12:13 PM, Andrew Woodward wrote: > I'd like to propose the creation of a puppet module to make use of Puppet > Application orchestrator. This would consist of a Puppet-4 compatible module > that would define applications that would wrap the existing

Re: [openstack-dev] [infra][neutron] - best way to load 8021q kernel module into cirros

On Mon, 8 Aug 2016, Jeremy Stanley wrote: > On 2016-08-08 11:20:54 +0200 (+0200), Miguel Angel Ajo Pelayo wrote: > > The problem with the other projects image builds is that they are > > based for bigger systems, while cirros is an embedded-device-like > > image which boots in a couple of

Re: [openstack-dev] [tripleo] Testing optional composable services in the CI

On 08/15/2016 10:54 AM, Dmitry Tantsur wrote: Hi everyone, happy Monday :) I'd like to start the discussion about CI-testing the optional composable services in the CI (I'm primarily interested in Ironic, but I know there are a lot more). thanks for bringing this up, with "pluggability" comes

Re: [openstack-dev] [vitrage] reference a type of alarm in template

Hi Yujun, The template example you are looking at is invalid. I added a new valid example (see the following link: https://review.openstack.org/#/c/355840/) As Elisha wrote, the ‘type’ field means the alarm type itself or in simple words where it was generated (Vitrage/Nagios/Zabbix/AODH) The

[openstack-dev] [tripleo] TripleO-Quickstart Driven Doc Generation Updates

Greetings All, Detailed post TripleO-Quickstart build doc generation is coming along smoothly. After much discussion between myself, adarazs, weshay, and larsks -- I believe to have found a solution that impacts TripleO-Quickstart and external roles minimally. Combining work from trown[1] and an

[openstack-dev] [Heat] Current status of observe reality feature implementation (Convergence Phase 2)

Hi all! I'd like to provide current status of observe reality implementation. I remember, that community wished to land before N release time as much observe reality patches as possible. Next resource plugins have observe reality feature patches on review and should be reviewed *as soon as

Re: [openstack-dev] [vitrage] reference a type of alarm in template

Hi, Liat, Thanks for clarification. But my question still remains. Under this definition (type <=> datasource), we can only refer to ***one** *alarm from each datasource in the template. Is it a limitation? How should I refer two different aodh alarms in the template? -- Yujun On Tue, Aug 16,

[openstack-dev] [tripleo] launchpad bugs

Hi team, This e-mail is addressed to TripleO developers interested by helping in bug triage. If you already subscribed to TripleO bugs notifications, you can skip and go at the second part of the e-mail. If not, please: 1) Go on https://bugs.launchpad.net/tripleo/+subscriptions 2) Click on "Add a

Re: [openstack-dev] [Kuryr] Overlay MTU setup in docker remote driver

Hi Ihar, Thanks for your comments. Agree, kuryr need to load mtu in neutron network. I submit a bug to track this: https://bugs.launchpad.net/kuryr-libnetwork/+bug/1613528 And patch sets are here: https://review.openstack.org/#/c/355712/ https://review.openstack.org/#/c/355714/ Generally,

Re: [openstack-dev] [puppet] weekly meeting #90

rrow at 3pm UTC on #openstack-meeting-4 > > Here's a first agenda: > https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20160816 > > > Feel free to add topics, and any outstanding bug and patch. > > See you tomorrow! > Thanks, > > > -- > ~~

Re: [openstack-dev] [tripleo] Testing optional composable services in the CI

On Tue, Aug 16, 2016 at 4:49 PM, James Slagle wrote: > On Mon, Aug 15, 2016 at 4:54 AM, Dmitry Tantsur wrote: >> Hi everyone, happy Monday :) >> >> I'd like to start the discussion about CI-testing the optional composable >> services in the CI (I'm

Re: [openstack-dev] [Kuryr] Overlay MTU setup in docker remote driver

Liping Mao (limao) wrote: Hi Kuryr team, When the network in neutron using overlay for vm, it will use dhcp option to control the VM interface MTU, but for docker, the ip address does not get from dhcp. So it will not set up proper MTU in container. Two work-around in my

Re: [openstack-dev] [Kuryr] Overlay MTU setup in docker remote driver

On Tue, Aug 16, 2016 at 6:29 AM, Liping Mao (limao) wrote: > Hi Kuryr team, > > I just notice, this can be fixed in kuryr bind code. > I submit a bug to track this: > https://bugs.launchpad.net/kuryr-libnetwork/+bug/1613528 > > And patch sets are here: >

Re: [openstack-dev] [Heat][Horizon] Any guidelines for naming heat resource type names?

This sounds like a bug on the Horizon side. There is/was a patch regarding a similar issue with LBaaS v2 resources too. It's likely just an incorrect assumption in the logic processing these names. Rob On 16 Aug 2016 11:03 p.m., "Zane Bitter" >

[openstack-dev] [QA] Running Tempest tests for a customized cloud

Hello There, I’m currently playing with using Tempest as our integration tests for our internal and external clouds, facing some issues with api which are not supported in our cloud. For ex, listing domains isn’t supported for any user, due to this V3 Identity tests are failing. So I would like

[openstack-dev] [murano] Separating guides from murano developers documentation

Hi folks, at this moment all murano documentation (including admin & user guides) is published only in one place [0], but actually all other projects store there only developer documentation and guides are separated. I propose to follow same model with murano documentation. What do you think?

Re: [openstack-dev] [all][infra] Binary Package Dependencies - not only for Python

On 08/16/2016 05:38 PM, Brant Knudson wrote: > s bindep.txt meant to be used by anything other than OpenStack CI? (As > in, are packagers going to rely on it?) > > In keystone's bindep.txt, we have packages listed like: > > |libldap2-dev [platform:dpkg] | > > > -> Which is only needed if you

Re: [openstack-dev] [QA] Running Tempest tests for a customized cloud

Hi Cheran, Best practice depends on your test plan and what coverage you. Does your test plan covers V3 Identity tests ? If it does and its failing, you should modify to make it work for your environment. Fast way to move forward is to exclude those tests. -Punal On Tue, Aug 16, 2016 at 3:40

Re: [openstack-dev] [neutron][dvr][fip] fg device allocated private ip address

Hi Carl Thanks for reply. I was wondering how this works? fg device has one private ip address, and the interface on upstream router has two ip address, one is private ip address, and the other one is public ip address, Can fg device do arp proxy for this situation? 在 2016-08-03

Re: [openstack-dev] [QA] Running Tempest tests for a customized cloud

Hello Punal, We do support both V2 and V3, that’s just a example I’ve stated BTW. We do have our own integration tests which are pretty much covers all our integration points with openstack. But we would like to leverage the tempest while doing our upstream merge for openstack components in CI.

Re: [openstack-dev] [tacker] infra_driver and mgmt_driver

Hi Yong Sheng, Sorry, missed this email from earlier. Yes, absolutely. We should deprecate both of them in Newton and remove it from the API in Ocata. thanks, Sridhar On Tue, Aug 9, 2016 at 8:39 PM, gong_ys2004 wrote: > Hi Sridhar, > > You said in

[openstack-dev] [javascript] library api reference publishing

As an action from the javascript meeting, below is the summary of how to integrate jsdoc [1] generated api reference with sphinx document. Feel free to comment and discuss in today's meeting. - findings - openstack api ref is dedicated to describe RESTful interface

[openstack-dev] [vitrage][vitrage-dashboard] cropped entity information

In the topology view, the content of entity information is sometimes cropped when there are too many rows. Is there a way to peek the cropped content? [image: xbm5sl.jpg] -- Yujun __ OpenStack Development Mailing List (not

[openstack-dev] How do I get devstack with nova-network now?

My nova-net local.conf isn't working anymore apparently, neutron is still getting installed and run rather than nova-network even though I have this in my local.conf: stack@novanet:~$ cat devstack/local.conf | grep enable_service enable_service tempest enable_service n-net #enable_service

Re: [openstack-dev] [OpenStack-docs] [Magnum] Using common tooling for API docs

On Tue, Aug 16, 2016 at 1:05 AM, Shuu Mutou wrote: > Hi Anne, > > AFAIK, the API WG adopted Swagger (OpenAPI) as common tool for API docs. > Anne, has not the adoption been changed? Otherwise, do we need to maintain > much RST files also? > It does say either/or in the

Re: [openstack-dev] How do I get devstack with nova-network now?

On 8/16/2016 9:52 PM, Matt Riedemann wrote: My nova-net local.conf isn't working anymore apparently, neutron is still getting installed and run rather than nova-network even though I have this in my local.conf: stack@novanet:~$ cat devstack/local.conf | grep enable_service enable_service

Re: [openstack-dev] FW: [Ceilometer]:Duplicate messages with Ceilometer Kafka Publisher.

Hi Gordon, As suggested I pasted pipeline.yaml content to paste.openstack.org http://paste.openstack.org/show/558688/ With Best Regards Raghunath Dudyala Tata Consultancy Services Limited Mailto: raghunat...@tcs.com Website: http://www.tcs.com

Re: [openstack-dev] [kolla][osic] OSIC cluster status

Kollagues, Can we get an update from the APAC / US reps? The last I heard we were having trouble getting guests spawned on an external network so they could be accessible by Rally. There's been various people looking at this the past few days but overall unclear where we are and time is

Re: [openstack-dev] [manila] nfs-ganesha export modification issue

On 08/16/2016 08:42 AM, Ramana Raja wrote: On Thursday, June 30, 2016 6:07 PM, Alexey Ovchinnikov wrote: Hello everyone, here I will briefly summarize an export update problem one will encounter when using nfs-ganesha. While working on a driver that relies on

Re: [openstack-dev] [watcher] Nominate Prashanth Hari as core for watcher-specs

+1 Jean-Emile DARTOIS {P} Software Engineer Cloud Computing {T} +33 (0) 2 56 35 8260 {W} www.b-com.com De : Antoine Cabot Envoyé : mardi 16 août 2016 16:57 À : OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [watcher] Nominate Prashanth Hari as core for watcher-specs

+1 > On Aug 16, 2016, at 11:59 AM, Jean-Émile DARTOIS > wrote: > > +1 > > Jean-Emile > DARTOIS > > {P} Software Engineer > Cloud Computing > > {T} +33 (0) 2 56 35 8260 > {W} www.b-com.com > > > De : Antoine

Re: [openstack-dev] [Puppet] Puppet OpenStack Application Module

During our weekly meeting [1] we discussed about $topic. * Deploying a PE stack in our CI is not an option, we rely only on FOSS. * Some FOSS deployers doing orchestration (eg mcollective-choria, etc) do exist but it doesn't seem there is an official consensus about which one Puppetlabs does

[openstack-dev] [watcher] Nominate Prashanth Hari as core for watcher-specs

Hi Watcher team, I'd like to nominate Prashanth Hari as core contributor for watcher-specs. As a potential end-user for Watcher, Prashanth gave us a lot of good feedback since the Mitaka release. Please vote for his candidacy. Antoine

Re: [openstack-dev] [openstack-ansible] git repo in infra_repo container not working

Hi Linhao Lu, I expect that you might be hitting the fact that fastcgi is no longer available. Instead of using http the git protocol is now being used. See https://github.com/openstack/openstack-ansible-repo_server/commit/c87a8c1d4ca008e03e8dcef4160503b622d1fc1f for details. Operating from

Re: [openstack-dev] [TripleO] tripleo-common bugs, bug tracking and launchpad tags

On Tue, Aug 16, 2016 at 10:40 AM, Julie Pichon wrote: > On 19 July 2016 at 16:20, Steven Hardy wrote: >> On Mon, Jul 18, 2016 at 12:28:10PM +0100, Julie Pichon wrote: >>> Hi, >>> >>> On Friday Dougal mentioned on IRC that he hadn't realised there was a >>>

Re: [openstack-dev] [barbican] Secure Setup & HSM-plugin

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Manuel, Historically all of our contributors working with the PKCS#11 crypto plugin have been using Safenet HSMs, which is why the Safenet mechanism is the default. The "CKR_MECHANISM_PARAM_INVALID" error appears to be a bug. You may file a

[openstack-dev] [TripleO] Status of the validations and priority patches

Hey folks, Martin André and I have been working on adding validations into the TripleO workflow. And since the time for landing things in Neutron is getting closer, here are a few patches I'd like to call your attention to. This patchset adds the Mistral workflows the gui and cli need for

Re: [openstack-dev] [all][tc][ptl] establishing project-wide goals

Excerpts from Sean Dague's message of 2016-08-16 10:35:11 -0400: > On 08/16/2016 05:36 AM, Thierry Carrez wrote: > > John Dickinson wrote: > Excerpts from John Dickinson's message of 2016-08-12 16:04:42 -0700: > > [...] > > The proposed plan has a lot of good in it, and I'm really

Re: [openstack-dev] [oslo] RPC call not appearing to retry

Hi, Le 2016-08-15 04:50, Eric K a écrit : Hi all, I'm running into an issue with oslo-messaging PRC call not appearing to retry. If I do oslo_messaging.RPCClient(transport, target, timeout=5, retry=10).call(self.context, method, **kwargs) using a topic with no listeners, I consistently get the

[openstack-dev] [vitrage] Vitrage weekly IRC meeting is SKIPPED

Hi, Vitrage IRC meeting tomorrow (Aug 17) will be SKIPPED, as many Vitrage contributors are away. Thanks, Ifat. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [Openstack][Neutron] No DVR meeting this week.

Hi Folks, We will not be having our weekly DVR meeting this week. We will resume the meeting next week. Thanks Swami __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [nova] Nova API sub-team meeting

Hi, We have weekly Nova API meeting today. The meeting is being held Wednesday UTC1300 and irc channel is #openstack-meeting-4. The proposed agenda and meeting details are here: https://wiki.openstack.org/wiki/Meetings/NovaAPI Please feel free to add items to the agenda. Thanks

Re: [openstack-dev] How do I get devstack with nova-network now?

Hi Your local.conf like below code. You should add "disable_service n-net" , you can disable nova-network this comment. # Neutron # --- disable_service n-net enable_service neutron enable_service q-svc enable_service q-agt enable_service q-dhcp enable_service q-l3

Re: [openstack-dev] [Kuryr] Proposing vikasc for kuryr-libnetwork core

+1 , Vikas has been doing a great work on the project and is a good addition to the team. On Wed, Aug 17, 2016 at 12:54 AM, Antoni Segura Puimedon wrote: > Hi Kuryrs, > > I would like to propose Vikas Choudhary for the core team for the > kuryr-libnetwork subproject. Vikas