Re: [openstack-dev] [kolla] [bifrost] bifrost container poc update

On Sat, May 14, 2016 at 2:44 AM, Mooney, Sean K wrote: > Hi this is an update on where I am with my poc of creating a bifost > container for kolla. > > As of Wednesday evening I have reached my v0 poc goal > > > > That goal was to demonstrate it was easy bifrost in a

Re: [openstack-dev] [kolla] [bifrost] bifrost container poc update

From: "Mooney, Sean K" > Date: Friday, May 13, 2016 at 2:14 PM To: "OpenStack Development Mailing List (not for usage questions)" >, Steven Dake

Re: [openstack-dev] [nova] gate testing with lvm imagebackend

On 5/10/2016 4:51 PM, Matt Riedemann wrote: For the libvirt imagebackend refactor that mdbooth is working on, I have a POC devstack-gate change which runs with the lvm imagebackend in the libvirt driver [1]. The test results are mostly happy except for anything related to migrate (including

Re: [openstack-dev] [tc] supporting Go

Python 2.x will not be supported for much longer, and let¹s face it, Python is easy, but it just does not scale. Nor does Python have the performance characteristics that large, distributed systems require. Maybe Java could replace Python in OpenStack as the workhorse language. -- Deklan Dieterly

Re: [openstack-dev] [nova] api-ref sprint - Friday wrap up

On 5/13/2016 7:14 PM, Sean Dague wrote: On 05/09/2016 08:23 AM, Sean Dague wrote: There is a lot of work to be done to get the api-ref into a final state. Review / fix existing patches - https://review.openstack.org/#/q/project:openstack/nova+file:api-ref+status:open shows patches not yet

Re: [openstack-dev] [tc] supporting Go

On 05/13/2016 08:21 PM, Dieterly, Deklan wrote: If we allow Go, then we should also consider allowing JVM based languages. Nope. Don't get me wrong, I've written more than my fair share of Java in my career, and I like it, and I miss automated refactoring and real threads. I have nothing

Re: [openstack-dev] [tc] supporting Go

If we allow Go, then we should also consider allowing JVM based languages. -- Deklan Dieterly Senior Systems Software Engineer HPE On 5/13/16, 2:10 PM, "Adam Young" wrote: >Can we just up and support Go, please? I'm a C++ and C buff, but I >would not inflict either of

[openstack-dev] [Congress] Nominating Anusha Ramineni and Eric Kao for core reviewer

Hi all, I'm writing to nominate Anusha Ramineni and Eric Kao as Congress core reviewers. Both Anusha and Eric have been active and consistent contributors in terms of code, reviewing, and interacting with the community since September--for all of Mitaka and a few months before that. Anusha was

Re: [openstack-dev] [Neutron] support of NSH in networking-SFC

On 13 May 2016 at 16:01, Cathy Zhang wrote: > Hi Uri, > > > > Current networking-sfc API allows the user to specify the data path SFC > encapsulation mechanism and NSH could be one of the encapsulation options. > > But since OVS release has not supported the NSH yet, we

Re: [openstack-dev] [nova] api-ref sprint - Friday wrap up

On 05/09/2016 08:23 AM, Sean Dague wrote: There is a lot of work to be done to get the api-ref into a final state. Review / fix existing patches - https://review.openstack.org/#/q/project:openstack/nova+file:api-ref+status:open shows patches not yet merged. Please review them, and if there are

Re: [openstack-dev] [Neutron] support of NSH in networking-SFC

On 13 May 2016 at 16:10, Elzur, Uri wrote: > Hi Cathy > > > > Thank you for the quick response. This is the essence of my question – > does Neutron keep OvS as a gold standard and why > Not at all true. Neutron, the open source implementation, uses a variety of open

Re: [openstack-dev] [Neutron] support of NSH in networking-SFC

On 13 May 2016 at 15:02, Elzur, Uri wrote: > Hi Armando > > > > As an industry we are working on SFC for 3 years or so (more?). Still to > date, we are told we can’t get Neutron or even a Stadium project e.g. > networking-SFC to support NSH (in IETF LC phase) because OvS has

[openstack-dev] [horizon] [javascript] Async file uploads in a new JS-centric UI

Hello, fellow web developers! I'd like to share some of my thoughts and findings that I made during playing with ng-file-upload [1] for file uploads in Swift UI and Create Image wizard in Horizon (both Angular). Sorry for a long letter, couldn't put it shorter (TL;DR => go to CONCLUSION section).

Re: [openstack-dev] [Neutron] support of NSH in networking-SFC

Hi Cathy Thank you for the quick response. This is the essence of my question – does Neutron keep OvS as a gold standard and why And if so does that apply to stadium projects As to OvS features, I guess the OvS ml is a better place, but wonder if the Neutron community wants to hold itself

Re: [openstack-dev] [Neutron] support of NSH in networking-SFC

Hi Uri, Current networking-sfc API allows the user to specify the data path SFC encapsulation mechanism and NSH could be one of the encapsulation options. But since OVS release has not supported the NSH yet, we have to wait until NSH is added into OVS and then start to support the NSH

Re: [openstack-dev] [Freezer] Replace Gnu Tar with DAR

When using incremental backups, tar will not handle removing a dir and then renaming another dir to the removed dir. dek@dek-HP-Z620-Workstation:~/backup-test$ tar --extract --listed-incrementa=/dev/null --file backup.2.tar tar: Cannot rename Œbackup/dir1¹ to Œbackup/dir2¹: Directory not empty

[openstack-dev] [Neutron][QA] Call to action - Neutron/Tempest API tests dedup

TL;DR: I'm looking for volunteers for tasks 1, 2 and 3 listed below. Help would be hugely appreciated and %(local_drink)s will be bought in Barcelona. I've posted example patches that demonstrate the idea. Needless to say I'm here to provide reviews and to answer questions. Additionally, most of

Re: [openstack-dev] [keystone][oslo][designate][zaqar][nova][swift] using pylibmc instead of python-memcached

On Fri, May 13, 2016 at 1:12 PM, Adam Young wrote: > On 05/13/2016 12:52 PM, Monty Taylor wrote: > >> On 05/13/2016 11:38 AM, Eric Larson wrote: >> >>> Monty Taylor writes: >>> >>> On 05/13/2016 08:23 AM, Mehdi Abaakouk wrote: > On Fri, May 13, 2016 at 02:58:08PM

Re: [openstack-dev] [Freezer] Replace Gnu Tar with DAR

On Fri, May 13, 2016 at 3:07 PM, Dieterly, Deklan wrote: > Does anybody see any issues if Freezer used DAR instead of Gnu Tar? DAR > seems to handle a particular use case that Freezer has while Gnu Tar does > not. > -- > Deklan Dieterly > > Senior Systems Software

Re: [openstack-dev] [Freezer] Replace Gnu Tar with DAR

Whats the issue? From: Dieterly, Deklan [deklan.diete...@hpe.com] Sent: Friday, May 13, 2016 3:07 PM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [Freezer] Replace Gnu Tar with DAR Does anybody see any issues if Freezer used DAR instead

Re: [openstack-dev] [glance] Newton priorities, processes, dates, spec owners and reviewers

I was hoping that this thread won't be a discussion thread because it's meant to be an announcement and I did encourage people to send me feedback last week/meeting and on the ML too so that we can come up with something that we can stick to. I wanted to send this out as early. Also, some

[openstack-dev] [Docs] Enhance Docs Landing Page Descriptive Text

Hi everyone, In the current Ubuntu install guide, there is this section:http://docs.openstack.org/mitaka/install-guide-ubuntu/common/app_support.html It contains a good deal of description on the type of information contained in each of the release-level docs. This type of description is very

[openstack-dev] [Freezer] Replace Gnu Tar with DAR

Does anybody see any issues if Freezer used DAR instead of Gnu Tar? DAR seems to handle a particular use case that Freezer has while Gnu Tar does not. -- Deklan Dieterly Senior Systems Software Engineer HPE __ OpenStack

[openstack-dev] [Neutron] support of NSH in networking-SFC

Hi Armando As an industry we are working on SFC for 3 years or so (more?). Still to date, we are told we can’t get Neutron or even a Stadium project e.g. networking-SFC to support NSH (in IETF LC phase) because OvS has not supported NSH. Is this an official position of Neutron that OvS is the

Re: [openstack-dev] [Congress] driver (authentication issue)

Hi Yue, Added the mailing list to this one too. Responses inline. If you're comfortable with IRC, you can go to the #congress channel on chat.freenode.net to ask question in real time. Would likely be quicker than debugging over email. On Fri, May 13, 2016 at 2:03 PM Yue Xin

[openstack-dev] [kolla] [bifrost] bifrost container poc update

Hi this is an update on where I am with my poc of creating a bifost container for kolla. As of Wednesday evening I have reached my v0 poc goal That goal was to demonstrate it was easy bifrost in a container with little to know changes. This is further broken down as follows. -Create

Re: [openstack-dev] [Congress] with vm-placement and the third party module

Hi Yue, Not sure I understood your question exactly. You can definitely build your own datasource and have it do whatever you want. The one I created had all the vm-placement logic that was contained in policy_engines/vmplacement.py. And in the commit it shows how to invoke the different

Re: [openstack-dev] [Openstack-operators] [glance] glance-registry deprecation: Request for feedback

On 5/13/16 4:29 PM, Flavio Percoco wrote: > On 13/05/16 15:52 -0400, Nikhil Komawar wrote: >> >> >> On 5/13/16 3:36 PM, Flavio Percoco wrote: >>> On 12/05/16 21:41 -0400, Nikhil Komawar wrote: I have been of the same opinion as far as upgrades go. I think we are stepping ahead of

Re: [openstack-dev] [Openstack-operators] [glance] glance-registry deprecation: Request for feedback

On 13/05/16 15:52 -0400, Nikhil Komawar wrote: On 5/13/16 3:36 PM, Flavio Percoco wrote: On 12/05/16 21:41 -0400, Nikhil Komawar wrote: I have been of the same opinion as far as upgrades go. I think we are stepping ahead of ourselves here a bit. We need to figure out the rolling upgrade

Re: [openstack-dev] [glance] Newton priorities, processes, dates, spec owners and reviewers

On 12/05/16 01:44 -0400, Nikhil Komawar wrote: Hello all, Here are a few important announcements for the members involved in the Glance community. Priorities: === * The Glance priorities for Newton were discussed at the contributors' meetup at summit. * There are a few items that were

Re: [openstack-dev] [keystone][oslo][designate][zaqar][nova][swift] using pylibmc instead of python-memcached

On 05/13/2016 12:52 PM, Monty Taylor wrote: On 05/13/2016 11:38 AM, Eric Larson wrote: Monty Taylor writes: On 05/13/2016 08:23 AM, Mehdi Abaakouk wrote: On Fri, May 13, 2016 at 02:58:08PM +0200, Julien Danjou wrote: What's wrong with pymemcache, that we picked for tooz and are using for 2

Re: [openstack-dev] [tc] supporting Go

Can we just up and support Go, please? I'm a C++ and C buff, but I would not inflict either of those on other people, nor would I want to support their code. Go is designed to be native but readable/writable. There is nothing perfect in this world. Python for most things. Javascript for web

Re: [openstack-dev] [Openstack-operators] [glance] glance-registry deprecation: Request for feedback

On 5/13/16 3:29 PM, Flavio Percoco wrote: > On 12/05/16 20:06 -0400, Nikhil Komawar wrote: >> The copy-from case is only in v1. >> >> >> For v2, I am having discussion with Doug, Morgan and Mike (TC) members >> as well as Chris (interop engineer with foundation) to ensure that we >> can actually

Re: [openstack-dev] [Openstack-operators] [glance] glance-registry deprecation: Request for feedback

On 5/13/16 3:36 PM, Flavio Percoco wrote: > On 12/05/16 21:41 -0400, Nikhil Komawar wrote: >> I have been of the same opinion as far as upgrades go. >> >> I think we are stepping ahead of ourselves here a bit. We need to >> figure out >> the rolling upgrade story first and see if registry is

Re: [openstack-dev] [Openstack-operators] [glance] glance-registry deprecation: Request for feedback

On 12/05/16 21:41 -0400, Nikhil Komawar wrote: I have been of the same opinion as far as upgrades go. I think we are stepping ahead of ourselves here a bit. We need to figure out the rolling upgrade story first and see if registry is actually useful or not there as well. I kinda disagree,

Re: [openstack-dev] [Openstack-operators] [glance] glance-registry deprecation: Request for feedback

On 12/05/16 20:06 -0400, Nikhil Komawar wrote: The copy-from case is only in v1. For v2, I am having discussion with Doug, Morgan and Mike (TC) members as well as Chris (interop engineer with foundation) to ensure that we can actually support copy-from in v2 for end users. I will add you to

Re: [openstack-dev] [magnum] How to document 'labels'

Ton, It seems the approach you proposed requires the yaml file that describes all the labels to be copied between repos (openstack/magnum, openstack/python-magnumclient, openstack/magnum-ui). Unless we setup a CI job to copy the file, I don't think it can solve the maintenance problem. Best

Re: [openstack-dev] [magnum] How to document 'labels'

Shu, You mentioned that Swagger was promoted by the API-WG. I wonder if they mention how to use it. For example, use it to generate the API document, generate an API client stub, or generate the CLI? In general, I see Swagger could solve the problem, but it does incur a significant amount of

Re: [openstack-dev] [kolla] Vagrant environment for kolla-kubernetes

Jeff, I'd like to see Kolla defaults for k8s come from one place rather then two, so I suggested to Dims in a previous review to depend on the kolla repo for those files rather then copy them and maintain them in two places. Therefore, I don¹t see a viable path forward without the Kolla package

Re: [openstack-dev] [ironic][nova][neutron][qa] Injecting code into grenade resource create phase

> From: Jim Rollenhagen [mailto:j...@jimrollenhagen.com] > On Thu, May 12, 2016 at 06:48:02AM -0400, Sean Dague wrote: > > Let me make sure I understand the crux of the issue: services may need > > to create additional custom networking in order for the rest of the > > resource flow to work

Re: [openstack-dev] [kolla] Vagrant environment for kolla-kubernetes

On Fri, May 13, 2016 at 2:57 AM, Britt Houser (bhouser) wrote: > Would we ever run AIO-k8s vagrant w/o Kolla repo? If not, then it makes > sense to me just to extend Vagrant kolla repo. > > Thx, > britt As Kolla developers we may not, but somebody else may want to. Either

Re: [openstack-dev] [magnum] Jinja2 for Heat template

Sounds good to me. Best regards, Hongbin From: Yuanying OTSUKA [mailto:yuany...@oeilvert.org] Sent: May-12-16 9:12 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] Jinja2 for Heat template Hi, My concern is that using option 1 is

Re: [openstack-dev] [oslo.service] Lifecycle Hooks

Excerpts from Kanagaraj Manickam's message of 2016-05-13 14:46:06 +0530: > DIms, > > Use case could be anything, which would needed by either > operator/community, who wants to perform an required task before and after > service is started. This requirement is very generic by nature, and I >

Re: [openstack-dev] [Monasca] Sporadic metrics

Hi Witek, Thank you for your response, it was really helpful. I was trying to figure out what are the next steps in the sporadics metrics side and you've made them more clear now. I'll report to my team so we can start the work. :) Best regards, Erickson Santos. - Mensagem original -

Re: [openstack-dev] [tc] supporting Go

Excerpts from Dmitry Tantsur's message of 2016-05-13 01:14:02 -0700: > On 05/11/2016 09:50 PM, Eric Larson wrote: > > To contrast that, the go POC was able to use a well tested go DNS > > library and implement the same documented interface that was then > > testable via the same functional tests.

[openstack-dev] [all][release] change in release announcement emails

The release team has recently landed a change to the script that generates the automated release announcement emails send to openstack-dev and openstack-announce when a project is released [1]. Based on feedback we received before and during the summit, we have changed the subject lines to

Re: [openstack-dev] [glance] [VMT] [Security] Proposal to add Brian Rosmaita to the glance-coresec team

On 05/13/2016 12:44 AM, Jeremy Stanley wrote: > On 2016-05-12 17:38:22 -0400 (-0400), Nikhil Komawar wrote: >> On 5/12/16 8:35 AM, Jeremy Stanley wrote: > [...] >>> While the size I picked in item #2 at >>> >> https://governance.openstack.org/reference/tags/vulnerability_managed.html#requirements

Re: [openstack-dev] [glance] [VMT] [Security] Proposal to add Brian Rosmaita to the glance-coresec team

On 05/12/2016 03:39 AM, Nikhil Komawar wrote: > Hello all, > > I would like to propose adding add Brian to the team. He has been doing > great work on improving the Glance experience for user and operators and > tying the threads with the security aspects of the service. He also > brings in good

Re: [openstack-dev] [keystone][oslo][designate][zaqar][nova][swift] using pylibmc instead of python-memcached

On 05/13/2016 11:38 AM, Eric Larson wrote: > > Monty Taylor writes: > >> On 05/13/2016 08:23 AM, Mehdi Abaakouk wrote: >>> On Fri, May 13, 2016 at 02:58:08PM +0200, Julien Danjou wrote: What's wrong with pymemcache, that we picked for tooz and are using for 2 years now?

Re: [openstack-dev] [Openstack-operators] [glance] glance-registry deprecation: Request for feedback

-Original Message- From: Fox, Kevin M Reply: Fox, Kevin M Date: May 12, 2016 at 19:00:12 To: Matt Fischer , Flavio Percoco Cc: openstack-dev@lists.openstack.org ,

Re: [openstack-dev] [tc] supporting Go

On Fri, 13 May 2016 10:14:02 +0200 Dmitry Tantsur wrote: > [...] If familiarity for Python > developers is an argument here, mastering Cython or making OpenStack run > on PyPy must be much easier for a random Python developer out there to > seriously bump the performance.

Re: [openstack-dev] [keystone][oslo][designate][zaqar][nova][swift] using pylibmc instead of python-memcached

Monty Taylor writes: On 05/13/2016 08:23 AM, Mehdi Abaakouk wrote: On Fri, May 13, 2016 at 02:58:08PM +0200, Julien Danjou wrote: What's wrong with pymemcache, that we picked for tooz and are using for 2 years now? https://github.com/pinterest/pymemcache Looks like a good alternative.

Re: [openstack-dev] [sahara] Nominating new members to Sahara Core

On Fri, May 13, 2016 at 11:33 AM, Vitaly Gridnev wrote: > Hello Sahara core folks! > > I'd like to bring the following folks to Sahara Core: > > 1. Lu Huichun > 2. Nikita Konovalov > 3. Chad Roberts > > Let's vote with +2/-2 for additions above. > > [0]

Re: [openstack-dev] [tc] supporting Go

You're absolutely right. If we can get as good (or even close) to the same performance eg with PyPy, then we should absolutely do that! I've had many public and private conversations over the last year or so that have that same basic message as I've been looking at the ongoing Golang work in

Re: [openstack-dev] [keystone][oslo][designate][zaqar][nova][swift] using pylibmc instead of python-memcached

On 05/13/2016 08:23 AM, Mehdi Abaakouk wrote: > On Fri, May 13, 2016 at 02:58:08PM +0200, Julien Danjou wrote: >> What's wrong with pymemcache, that we picked for tooz and are using for >> 2 years now? >> >> https://github.com/pinterest/pymemcache > > Looks like a good alternative. Honestly,

Re: [openstack-dev] [keystone][oslo][designate][zaqar][nova][swift] using pylibmc instead of python-memcached

On Fri, May 13, 2016 at 6:23 AM, Mehdi Abaakouk wrote: > On Fri, May 13, 2016 at 02:58:08PM +0200, Julien Danjou wrote: > >> What's wrong with pymemcache, that we picked for tooz and are using for >> 2 years now? >> >> https://github.com/pinterest/pymemcache >> > > Looks like

[openstack-dev] [nova][scheduler] Next meeting: Monday May 16 at 1400 UTC

The next meeting of the Nova Scheduler subteam will be help in #openstack-meeting-alt on Monday, May 16 at 1400 UTC. http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160516T14 If you have any specs or patches that you’d like to discuss, or items for the open discussion, please

[openstack-dev] [Monasca] Sporadic metrics

Hi Erickson, thanks for your interest in our project and sorry for replying so late. We are happy that you're willing to contribute to the development of sporadic metrics. The incentive for this development is to introduce the possibility to create alarms in Monasca based on event like

Re: [openstack-dev] [Fuel] Fuel - Rack Scale Architecture integration

Absolutely agree with Jay. Fuel is a community project. Please keep discussion public including technical details. Anyway, integration is welcome, please go ahead and create BP (btw, spec review request is the best place to discuss technical details). Vladimir Kozhukalov On Fri, May 13, 2016

[openstack-dev] [sahara] Nominating new members to Sahara Core

Hello Sahara core folks! I'd like to bring the following folks to Sahara Core: 1. Lu Huichun 2. Nikita Konovalov 3. Chad Roberts Let's vote with +2/-2 for additions above. [0] http://stackalytics.com/?module=sahara-group [1] http://stackalytics.com/?module=sahara-group=mitaka -- Best

Re: [openstack-dev] [kolla] Vagrant environment for kolla-kubernetes

On Fri, May 13, 2016 at 10:36 AM, Martin André wrote: > On Fri, May 13, 2016 at 8:57 AM, Britt Houser (bhouser) > wrote: >> Would we ever run AIO-k8s vagrant w/o Kolla repo? If not, then it makes >> sense to me just to extend Vagrant kolla repo. > >

Re: [openstack-dev] [keystone][oslo][designate][zaqar][nova][swift] using pylibmc instead of python-memcached

On 13 May 2016, at 1:14, Steve Martinelli wrote: > /me gets the ball rolling > > Just when python3 support for keystone was looking like a reality, we've > hit another snag. Apparently there are several issues with python-memcached > in py3, putting it simply: it loads, but doesn't actually

Re: [openstack-dev] [cross-project][quotas][delimiter] Austin Summit - Design Session Summary

Hi Andreas, Thanks for your suggestions. Please find my response inline. On 5/13/16 2:45 AM, Andreas Jaeger wrote: > On 05/12/2016 10:58 PM, Nikhil Komawar wrote: >> [...] >> But we are not working in a corner, we've a representative from cinder, >> someone from trove who is interested in long

Re: [openstack-dev] [Fuel] Fuel - Rack Scale Architecture integration

On 05/13/2016 07:26 AM, Andrian Noga wrote: Hi Deepti, We have already a vision about Fuel-UI implementation for RSA. I've replied already to you in private email. Let's continue this thread in private conversation. Please, no. Fuel is an OpenStack Big Tent project. The Fuel roadmap,

Re: [openstack-dev] [Openstack-stable-maint] Stable check of openstack/trove failed

On 2016-05-13 12:53:36 + (+), Amrith Kumar wrote: > The interwebs must've been in need of some pluming work ... [...] If this ran in rax-ord then it's a known long-standing issue for us. I've had a support ticket open with them for weeks (since well before the summit) trying to get to the

Re: [openstack-dev] [keystone][oslo][designate][zaqar][nova][swift] using pylibmc instead of python-memcached

On Fri, May 13, 2016 at 02:58:08PM +0200, Julien Danjou wrote: What's wrong with pymemcache, that we picked for tooz and are using for 2 years now? https://github.com/pinterest/pymemcache Looks like a good alternative. -- Mehdi Abaakouk mail: sil...@sileht.net irc: sileht

Re: [openstack-dev] [keystone][oslo][designate][zaqar][nova][swift] using pylibmc instead of python-memcached

On Fri, May 13 2016, Steve Martinelli wrote: > /me gets the ball rolling > > Just when python3 support for keystone was looking like a reality, we've > hit another snag. Apparently there are several issues with python-memcached > in py3, putting it simply: it loads, but doesn't actually work.

Re: [openstack-dev] [Openstack-stable-maint] Stable check of openstack/trove failed

The interwebs must've been in need of some pluming work ... 2016-05-13 06:09:37.457 | git.exc.GitCommandError: 'git remote prune --dry-run origin' returned with exit code 128 2016-05-13 06:09:37.457 | stderr: 'fatal: unable to connect to git.openstack.org: 2016-05-13 06:09:37.457 |

Re: [openstack-dev] [keystone][oslo][designate][zaqar][nova][swift] using pylibmc instead of python-memcached

On May 13, 2016 05:32, "Kiall Mac Innes" wrote: > > Hey Dims, > > From what I remember, oslo.cache seemed unnecessarily complex to use > vs memcache's simplicity, and didn't have any usage docs[1] to help folks > get started using it. > > I can see there is some docs under the

Re: [openstack-dev] [tacker]ad-hoc meeting of May 16; now May 17

Hi, Date / Time change IRC meeting: https://webchat.freenode.net/?channels=tacker on Monday 17 starting from UTC 17:00. Agenda: # Tacker Ceilometer Monitoring Driver and Autoscaling Sync Best Regards Bruce Thompson ( brucet ) From: Bruce Thompson >

Re: [openstack-dev] [magnum] How to document 'labels'

Hi peers, Since Magnum-UI should display selectable values for user, so Magnum-UI wants to get available values from API. https://blueprints.launchpad.net/magnum/+spec/magnum-api-swagger-support https://bugs.launchpad.net/magnum-ui/+bug/1568890 And we don't want to write same things in many

Re: [openstack-dev] [tacker]ad-hoc meeting of May 16

Qiming, I don¹t think we will be discussing Senlin as part of the agenda in this meeting. Is there a Senlin topic that you believe should be covered? Bruce T On 5/12/16, 8:37 PM, "Qiming Teng" wrote: >UTC 16:00 is too late for most of senlin developers to

Re: [openstack-dev] [keystone][oslo][designate][zaqar][nova][swift] using pylibmc instead of python-memcached

Hey Dims, >From what I remember, oslo.cache seemed unnecessarily complex to use vs memcache's simplicity, and didn't have any usage docs[1] to help folks get started using it. I can see there is some docs under the module index, but at a glance they seem somewhat disconnected and incomplete.

Re: [openstack-dev] [keystone][oslo][designate][zaqar][nova][swift] using pylibmc instead of python-memcached

On May 13, 2016 05:25, "Mehdi Abaakouk" wrote: >>> >>> - Is anyone interested in using pylibmc in their project instead of >>> python-memcached? > > > This is not a real drop-in replacement, pylibmc.Client is not threadsafe > like python-memcached [1]. Aos it's written in C, it

Re: [openstack-dev] [openstack-ansible] LBaaSv2 / Octavia support

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 05/12/2016 11:42 PM, Xav Paice wrote: > Thanks for explaining that - I thought I was going mad. You're right about > implementation challenges! It's definitely a new way of doing things. I'm trying to get used to this new service VM model

Re: [openstack-dev] [keystone][oslo][designate][zaqar][nova][swift] using pylibmc instead of python-memcached

- Is anyone interested in using pylibmc in their project instead of python-memcached? This is not a real drop-in replacement, pylibmc.Client is not threadsafe like python-memcached [1]. Aos it's written in C, it shouldn't be a problem for keystone because you don't use eventlet anymore, but for

Re: [openstack-dev] [keystone][oslo][designate][zaqar][nova][swift] using pylibmc instead of python-memcached

On May 13, 2016 04:36, "Davanum Srinivas" wrote: > > Steve, > > Couple of points: > > * We can add pylibmc to g-r and phase out python-memcached over a time period. > * If folks are using python-memcached, we should switch then over to > oslo.cache, then only oslo.cache will

Re: [openstack-dev] [requirements] Cruft entries found in global-requirements.txt

netmiko is in networking-generic-switch requirements.txt https://github.com/openstack/networking-generic-switch/blob/master/requirements.txt#L2 On Sat, May 7, 2016 at 5:35 AM, Haïkel wrote: > Started on removing some entries, I guess I have big cleanup to do RDO >

Re: [openstack-dev] [keystone][oslo][designate][zaqar][nova][swift] using pylibmc instead of python-memcached

Steve, Couple of points: * We can add pylibmc to g-r and phase out python-memcached over a time period. * If folks are using python-memcached, we should switch then over to oslo.cache, then only oslo.cache will reference either python-memcached or pylibmc which will make the situation easier to

Re: [openstack-dev] [puppet] magnum module - fixes/improvements for Mitaka release

On Fri, May 13, 2016 at 9:42 AM, Michal Adamczyk wrote: > > > On Thu, May 12, 2016 at 2:14 PM, Michal Adamczyk > wrote: > >> >> On Wed, May 11, 2016 at 7:47 PM, Hongbin Lu >> wrote: >> >>> >>> >>> > -Original Message- >>>

Re: [openstack-dev] [Fuel] Fuel - Rack Scale Architecture integration

Hi Deepti, We have already a vision about Fuel-UI implementation for RSA. I've replied already to you in private email. Let's continue this thread in private conversation. Regards, Andrian Noga Engineering Manager Partner Integration Team, Mirantis, Inc. +38 (066) 811-84-12 Skype: bigfoot_ua

Re: [openstack-dev] [heat] [grenade] need for a testing phase?

On Thu, May 12, 2016 at 02:50:03PM -0400, Sean Dague wrote: > I just discovered this - > https://github.com/openstack/heat/blob/fed92fdd6e5a14ea658621375e528f1c0cbde944/devstack/upgrade/resources.sh#L41 > in looking at why - https://review.openstack.org/#/c/315501/ did not > pass on

Re: [openstack-dev] [cross-project][infra][keystone] Moving towards a Identity v3-only on Devstack - Next Steps

On 05/12/2016 08:49 PM, Steve Martinelli wrote: > > On Thu, May 12, 2016 at 6:39 PM, gordon chung > wrote: > > > can anyone confirm when we deprecated keystonev2? i see a bp[1] related > to deprecation that was 'implemented' in 2013. > > > We did

Re: [openstack-dev] [neutron][ovo] NeutronDbObject concurrency issues

> there is ongoing work to add the revision number Thanks for pointing out. Then I’ll stick with opt.2. > Then, the object should before update() fetch the current state and try to > merge the requested changes to the current state of the object I don’t think merging states automatically could

Re: [openstack-dev] [neutron][ovo] NeutronDbObject concurrency issues

>In a multi-writer galera cluster both SELECT FOR UPDATE and CAS won't fail >until commit time Good point, I did not consider multi-writer. But anyway, my point was that opt.2 is no worse than opt.1. > On 13 May 2016, at 12:04, Kevin Benton wrote: > > >While opt.2 only

Re: [openstack-dev] JavaScript RoadMap for OpenStack Newton

On 05/12/2016 06:27 PM, Michael Krotscheck wrote: > Responses inline: > > On 04/21/2016 04:35 PM, Michael Krotscheck wrote: > > New: Xenial Build Nodes > > > > As of two weeks ago, OpenStack’s Infrastructure is running a > version of > > Node.js and npm more recent than

Re: [openstack-dev] [oslo.service] Lifecycle Hooks

DIms, Use case could be anything, which would needed by either operator/community, who wants to perform an required task before and after service is started. This requirement is very generic by nature, and I believe it will be very useful. Would like to give the sample use cases from from

Re: [openstack-dev] [neutron][ovo] NeutronDbObject concurrency issues

>While opt.2 only prevents the conflicting changes, but does not guarantee that the object does not change while within the context, I'm not sure what you mean here. In a multi-writer galera cluster both SELECT FOR UPDATE and CAS won't fail until commit time if someone writes to another server.

Re: [openstack-dev] [tc] supporting Go

+ Agree. It is strange to use another language to address performance issues if you haven't tried to solve those issues using original language's options. On 05/13/2016 11:53 AM, Fausto Marzi wrote: ++ Brilliant. On Fri, May 13, 2016 at 10:14 AM, Dmitry Tantsur

Re: [openstack-dev] [neutron][ovo] NeutronDbObject concurrency issues

>What is left to be done in opt.2 is to handle situation when object is trying to update the state and the revision is not the latest. Once the revision counter is added, this will generate an error (StaleData I think) that will be caught by the retry decorator so the process can be started over

Re: [openstack-dev] [tc] supporting Go

++ Brilliant. On Fri, May 13, 2016 at 10:14 AM, Dmitry Tantsur wrote: > > This is pretty subjective, I would say. I personally don't feel Go > (especially its approach to error handling) any natural (at least no more > than Rust or Scala, for example). If familiarity for

Re: [openstack-dev] [puppet] magnum module - fixes/improvements for Mitaka release

On Thu, May 12, 2016 at 2:14 PM, Michal Adamczyk wrote: > > On Wed, May 11, 2016 at 7:47 PM, Hongbin Lu wrote: > >> >> >> > -Original Message- >> > From: Emilien Macchi [mailto:emil...@redhat.com] >> > Sent: May-11-16 9:44 AM >> > To:

Re: [openstack-dev] [kolla] Vagrant environment for kolla-kubernetes

On Fri, May 13, 2016 at 8:57 AM, Britt Houser (bhouser) wrote: > Would we ever run AIO-k8s vagrant w/o Kolla repo? If not, then it makes > sense to me just to extend Vagrant kolla repo. Agreed. Vagrant is for developers and developers will want the kolla repo for building

Re: [openstack-dev] [neutron][ovo] NeutronDbObject concurrency issues

Hi Ilya, Thanks for investigating the concurrency issue. It is indeed a problem from multithreaded neutron-server point of view. Regarding the opt.2, there is ongoing work to add the revision number[1] to main neutron resources (port, network, subnet...) This is connected to spec [2] and

Re: [openstack-dev] [tc] supporting Go

On 05/11/2016 09:50 PM, Eric Larson wrote: Flavio Percoco writes: On 11/05/16 09:47 -0500, Dean Troyer wrote: On Tue, May 10, 2016 at 5:54 PM, Flavio Percoco wrote: [language mixing bits were here] The above is my main concern with this proposal. I'vementioned

[openstack-dev] [keystone][oslo][designate][zaqar][nova][swift] using pylibmc instead of python-memcached

/me gets the ball rolling Just when python3 support for keystone was looking like a reality, we've hit another snag. Apparently there are several issues with python-memcached in py3, putting it simply: it loads, but doesn't actually work. I've included projects in the subject line that use

Re: [openstack-dev] [kolla] Vagrant environment for kolla-kubernetes

Would we ever run AIO-k8s vagrant w/o Kolla repo? If not, then it makes sense to me just to extend Vagrant kolla repo. Thx, britt On 5/13/16, 2:37 AM, "Michal Rostecki" wrote: >Hi, > >Currently we have nice guide about setting up AIO k8s environment in >review.

Re: [openstack-dev] [cross-project][quotas][delimiter] Austin Summit - Design Session Summary

On 05/12/2016 10:58 PM, Nikhil Komawar wrote: > [...] > But we are not working in a corner, we've a representative from cinder, > someone from trove who is interested in long term quota goals, someone > who has worked on nova (and then we are borrowing the gen_id concept of > Jay from Nova),

Re: [openstack-dev] [tc] supporting Go

On Tue 10 May at 10:19:23 -0400 raysonlo...@gmail.com said: > > IMO, the best use case of not using a package manager is when deploying into > containers -- would you prefer to just drop a static binary of your Go code, > or > you would rather install "apt-get" into a container image, and then

[openstack-dev] [kolla] Vagrant environment for kolla-kubernetes

Hi, Currently we have nice guide about setting up AIO k8s environment in review. But at the same time I'm thinking also about automating this by Vagrant, like we did in kolla-mesos. Here comes the question - what repo is good for keeping the Vagrant stuff for kolla-k8s? I see two options.

  1   2   >