Re: [openstack-dev] [Horizon] Proposing Kenji Ishii for core

+1 From: Timur Sufiev Reply-To: OpenStack List Date: Friday, November 18, 2016 at 1:34 AM To: OpenStack List Subject: Re: [openstack-dev] [Horizon] Proposing Kenji Ishii for core +1 On Fri, Nov 18,

Re: [openstack-dev] [Zun] Zun PTL election

Hi all, I nominated myself to be the Zun PTL. As the founder of this project, it is my honor to work with all of you to build an innovative container service for OpenStack. Zun is a new project but already attracted a diverse set of contributors. I want to take this chance to thank our talent

Re: [openstack-dev] [security] FIPS Compliance (Was: [requirements][kolla][security] pycrypto vs cryptography)

On 18 Nov 2016, at 8:14, Dean Troyer wrote: >> -Original Message- >> From: Luke Hinds > [...] >>> for non security related functions, but when it comes to government >>> compliance and running OpenStack on public clouds (and even private for the >>> Telcos / NFV),

Re: [openstack-dev] oaktree - a friendly end-user oriented API layer - anybody want to help?

Excerpts from Zane Bitter's message of 2016-11-17 18:24:35 -0500: > On 15/11/16 09:56, Monty Taylor wrote: > > Hey everybody! > > > > At this past OpenStack Summit the results of the Interop Challenge were > > shown on stage. It was pretty awesome - 17 different people from 17 > > different clouds

Re: [openstack-dev] oaktree - a friendly end-user oriented API layer - anybody want to help?

Excerpts from Zane Bitter's message of 2016-11-18 14:24:43 -0500: > On 17/11/16 19:01, Monty Taylor wrote: > > On 11/17/2016 05:24 PM, Zane Bitter wrote: > >> On 15/11/16 09:56, Monty Taylor wrote: > >>> Hey everybody! > >>> > >>> At this past OpenStack Summit the results of the Interop Challenge

Re: [openstack-dev] [Neutron] Stepping down from core

On Thu, Nov 17, 2016 at 1:42 PM, Carl Baldwin wrote: > Neutron (and Openstack), > > It is with regret that I report that my work situation has changed such that > I'm not able to keep up with my duties as a Neutron core reviewer, L3 > lieutenant, and drivers team member. My

Re: [openstack-dev] [docs][upgrades] time to add official docs for upgrading services?

Excerpts from Steve Martinelli's message of 2016-11-17 20:36:46 -0500: > In the keystone docs we have notes about how to upgrade between releases > [1], so does the nova team [2]. > > Is it time we create an official guides to [3] for this subject? > > [1]

Re: [openstack-dev] oaktree - a friendly end-user oriented API layer - anybody want to help?

On 17/11/16 19:01, Monty Taylor wrote: On 11/17/2016 05:24 PM, Zane Bitter wrote: On 15/11/16 09:56, Monty Taylor wrote: Hey everybody! At this past OpenStack Summit the results of the Interop Challenge were shown on stage. It was pretty awesome - 17 different people from 17 different clouds

Re: [openstack-dev] [all] [Rally] broken jobs

yse, I think you are right. On Fri, Nov 18, 2016 at 4:04 PM, gordon chung wrote: > this seems related to fact we use datetime type in mysql which requires > 5.6.4? (i'm guessing on version). but yes, ubuntu-xenial should have the > required mysql. > > On 18/11/16 07:50 AM, Andrey

Re: [openstack-dev] [neutron-lbaas][octavia] About playing Neutron LBaaS

Hi Yipei, A note, that you probably want to use the tags [neutron-lbaas] and [octavia] instead of [tricicle] to catch the LBaaS team attention. Since you are using the octavia driver, can you please include a link to your o-cw.log? This will tell us why the load balancer create failed. Also, I

Re: [openstack-dev] [kolla] Obtaining version information for Docker container

So just something that I can share about what we are putting in our images, since they are getting built from jenkins we shove in pretty much all the jenkins build information into it: $ IMG="" $ docker run $IMG cat /jenkins.json { "Project": "glance", "Project git":

Re: [openstack-dev] [architecture] Reminder: Arch-WG Meeting today, and -- repo

Apologies for last week, it completely slipped my mind while I was traveling. The EU meeting time is now 2000 UTC, which is very early in the morning for most of Asia. I'll try to be better about running the APAC friendly time slot. Excerpts from Zhipeng Huang's message of 2016-11-18 17:07:21

Re: [openstack-dev] [kolla] Obtaining version information for Docker container

I've been thinking about this a bit as well, and think that we should consider using the docker label schema (http://label-schema.org/rc1/) as a solution for #1, it would be possible to add labeling to kolla-build to add these labels simply. This solution is gaining traction in the docker

Re: [openstack-dev] [kolla] Source build gates are now voting

great! 2016-11-18 14:51 GMT-03:00 Michał Jastrzębski : > Hello, > > Since we split ansible, we can now afford to have some voting gates, > for start - source build gates for 3 major distros are now voting. > > Cheers, > Michal > >

[openstack-dev] [kolla] Source build gates are now voting

Hello, Since we split ansible, we can now afford to have some voting gates, for start - source build gates for 3 major distros are now voting. Cheers, Michal __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [neutron][metadata] Is there HTTP attack issue in metadata proxy functionality offered by reference implementation?

Thant’s remind me when we tried to improve cloud-init. Basically, the discovery process checks sequentially where the instance is being landed(EC2, GoogleCompute, OpenStack). This process could be done in parallel and reduce the time to boot. Regards, Victor Morales On 11/16/16, 11:31

Re: [openstack-dev] [kolla] Obtaining version information for Docker container

Steve, (And the rest of kolla) This raises a question I've had for a while and wanted to talk through. Right now, kolla versions containers based on the kolla version (packaging version). In most package managers dpkg/rpm/etc, the versioning is done in a very different way. The software

Re: [openstack-dev] [Neutron] Stepping down from core

Hey Carl, These are sad news, thanks for those years helping to make OpenStack better, best of the wishes for your future assignments. Thanks, Victor Morales From: Carl Baldwin > Reply-To: "OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [magnum] Managing cluster drivers as individual distro packages

If we were to go with (2), what should happen to the common code? From: Spyros Trigazis > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > Date:

Re: [openstack-dev] [Neutron] Stepping down from core

Sad to see you stepping down. Thanks for making Neutron better and good luck in your new adventures! Jakub On 17/11/2016 19:42, Carl Baldwin wrote: Neutron (and Openstack), It is with regret that I report that my work situation has changed such that I'm not able to keep up with my duties as

[openstack-dev] Subscribe to release-announces to get future OpenStack release announcements !

Hi everyone, As OpenStack produces more deliverables (and some projects do frequent intermediary releases within the cycle), release announcements have been creating a lot of noise on the openstack-announce and openstack-dev mailing-lists, sometimes creating distraction away from more important

Re: [openstack-dev] [security] FIPS Compliance (Was: [requirements][kolla][security] pycrypto vs cryptography)

-Original Message- From: Dean Troyer Reply: OpenStack Development Mailing List (not for usage questions) Date: November 18, 2016 at 10:15:44 To: OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [security] FIPS Compliance (Was: [requirements][kolla][security] pycrypto vs cryptography)

> -Original Message- > From: Luke Hinds [...] >> for non security related functions, but when it comes to government >> compliance and running OpenStack on public clouds (and even private for the >> Telcos / NFV), not meeting FIPS will in some cases block production

Re: [openstack-dev] [Neutron] Stepping down from core

Thank you for your guidance and support Carl. Appreciate it. All the best for future endeavors. Regards, Aradhana From: Carl Baldwin [mailto:c...@ecbaldwin.net] Sent: Thursday, November 17, 2016 12:43 PM To: OpenStack Development Mailing List Subject:

Re: [openstack-dev] [git-upstream] [Duplicate Changes] How to view only commits applied since last import

On 18/11/16 15:27, Darragh Bailey - mailing lists wrote: > > At this point, now you'll see X, X' & X'', and Y, Y' & Y''. Obviously > this cause a bit of confusion when listing the changes using: > > git log --oneline --graph E~1..local/mitaka > > you see something like the following (see

[openstack-dev] [security] FIPS Compliance (Was: [requirements][kolla][security] pycrypto vs cryptography)

  -Original Message- From: Luke Hinds Reply: OpenStack Development Mailing List (not for usage questions) Date: November 18, 2016 at 08:43:42 To: OpenStack Development Mailing List (not for usage questions)

[openstack-dev] [watcher] Barcelona summit summary

Hi We had a super productive summit with many very active participants. Thanks to everybody who participated. Detailed minutes are available at: https://etherpad.openstack.org/p/watcher-ocata-design-session We had a talk and 4 Watcher sessions during the summit. - The *first session*

Re: [openstack-dev] [git-upstream] [Duplicate Changes] How to view only commits applied since last import

On 17/11/16 12:47, Paul Bourke wrote: > Hi Darragh / git-upstream community, > > I've been looking at a way to easily view a log of what commits made > since the last upstream import when managing a branch with git-upstream. > Right now this can be hard to do - something like 'git log >

Re: [openstack-dev] [devstack] Specify OpenvSwitch version in local.conf

On 11/18/2016 07:33 AM, zhi wrote: hi, all. I have a quick question about devstack. Can I specify OpenvSwitch version in local.conf when during the installation of devstack? I want to OVS 2.6.0 in my devstack. Can I specify it? Thanks Zhi Chang

Re: [openstack-dev] [docs][upgrades] time to add official docs for upgrading services?

Yes, I think it’s time to create a specific guide for this. It’s a topic of high interest for Operators (current and future) and helping them to understand how to plan their deployment for upgradability (ideally non-disruptive upgrades) would be very valuable. Carol From: Steve Martinelli

Re: [openstack-dev] [Neutron] Stepping down from core

On 2016-11-17 01:42 PM, Carl Baldwin wrote: Neutron (and Openstack), It is with regret that I report that my work situation has changed such that I'm not able to keep up with my duties as a Neutron core reviewer, L3 lieutenant, and drivers team member. My participation has dropped off

[openstack-dev] [new][documentation] openstack-doc-tools 1.2.1 release

We are frolicsome to announce the release of: openstack-doc-tools 1.2.1: Tools for OpenStack Documentation The source is available from: http://git.openstack.org/cgit/openstack/openstack-doc-tools Download the package from: https://tarballs.openstack.org/openstack-doc-tools/ Please

Re: [openstack-dev] Fwd: Re: [requirements][kolla][security] pycrypto vs cryptography

On 2016-11-18 14:38:22 + (+), Luke Hinds wrote: [...] > I proposed raising bugs on launchpad for each instance discovered, so that > if anything, we at least have an idea of the extent of work needed to reach > the needed level of compliance for FIPS 140-2. [...] It's come up plenty over

Re: [openstack-dev] [Neutron] Stepping down from core

Carl, Sad to see this happening. I've learned a lot from you. Good luck Cheers On Thu, Nov 17, 2016 at 12:42 PM, Carl Baldwin wrote: > Neutron (and Openstack), > > It is with regret that I report that my work situation has changed such > that I'm not able to keep up with

Re: [openstack-dev] [kolla][git]How to backport commit after repo split

On 2016-11-17 23:10:50 -0500 (-0500), Juan L. Negron wrote: > At some point, it would be good if the kolla-ansible repo is added > as a submodule of the kolla one to simplify things. This already came up here this week in a related thread on the repo split, and then again at the Kolla meeting. I

Re: [openstack-dev] Fwd: Re: [requirements][kolla][security] pycrypto vs cryptography

Hi, I missed this thread, so top posting with a related topic.. We discussed FIPS 140-2 yesterday in the OSSP irc meeting. I recently tried running OpenStack on a FIPS 140-2 enabled kernel in CentOS, and all of instances of MD5 use (mainly hashlib.md5) were rejected resulting in the various

[openstack-dev] [magnum] Managing cluster drivers as individual distro packages

Hi all, In magnum, we implement cluster drivers for the different combinations of COEs (Container Orchestration Engines) and Operating Systems. The reasoning behind it is to better encapsulate driver-specific logic and to allow operators deploy custom drivers with their deployment specific

Re: [openstack-dev] [Neutron] custom rules - security groups

Actually for our case we want to manage it in a different way. From: Ihar Hrachyshka [ihrac...@redhat.com] Sent: 18 November 2016 14:41 To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron] > On 18 Nov

Re: [openstack-dev] [all] [Rally] broken jobs

this seems related to fact we use datetime type in mysql which requires 5.6.4? (i'm guessing on version). but yes, ubuntu-xenial should have the required mysql. On 18/11/16 07:50 AM, Andrey Kurilin wrote: > Hi stackers, > > I hate to report such things, but most of rally jobs are broken now due

Re: [openstack-dev] [Neutron] Stepping down from core

On Thu, Nov 17, 2016 at 6:44 PM Carl Baldwin wrote: > Neutron (and Openstack), > > It is with regret that I report that my work situation has changed such > that I'm not able to keep up with my duties as a Neutron core reviewer, L3 > lieutenant, and drivers team member. My

Re: [openstack-dev] [neutron]

> On 18 Nov 2016, at 13:58, Iago Santos Pardo wrote: > > Hello, > > We are using Neutron with the linuxbridge plugin and security groups enabled > and we have some custom rules in iptables running on the compute nodes. When > the agent rebuilds the firewall it

Re: [openstack-dev] [neutron]

Hello, AFAIK, it's not possible. I did a similar thing by extending neutron iptables driver in order to set "pre-rules". Best regards, Cédric/ZZelle On Fri, Nov 18, 2016 at 1:58 PM, Iago Santos Pardo < iago.santos.pa...@cern.ch> wrote: > Hello, > > We are using Neutron with the linuxbridge

[openstack-dev] [neutron]

Hello, We are using Neutron with the linuxbridge plugin and security groups enabled and we have some custom rules in iptables running on the compute nodes. When the agent rebuilds the firewall it changes the rules order, putting the neutron chains on the top. Is there any way to preserve the

Re: [openstack-dev] [git-upstream] [Additional Branches] How to view only commits applied since last import

On 17/11/16 12:47, Paul Bourke wrote: > Hi Darragh / git-upstream community, My current understanding is we have a branch, that consists of a mixture > of upstream commits from previous imports, and custom commits. We want > to show a list of commits added since the last import. However, if

Re: [openstack-dev] [OpenStack-docs] [OpenStack-operators] [docs][upgrades] time to add official docs for upgrading services?

On Thu, Nov 17, 2016 at 11:04 PM, darren chan wrote: > Good timing, I was about to send a follow-up email about this spec. > > I agree, this content needs to be more visible, which is why the spec > proposed to move upgrade notes to the Upgrades chapter in the Operations

[openstack-dev] [all] [Rally] broken jobs

Hi stackers, I hate to report such things, but most of rally jobs are broken now due to uncompatibility aodh service with ubuntu-trusty nodes. If you find failed rally jobs with http://paste.openstack.org/show/589707/ in devstacklogs, recheck will not help. I'm working on two changes now for

Re: [openstack-dev] [git-upstream] How to view only commits applied since last import

Hi Paul This might be a bit long, noticed a few more items to be added to the documentation for git-upstream. Good thing documentation is the major item for the next release ;-) After an initial attempt at writing one response, I've decided to break it up a bit into a couple of emails, because

Re: [openstack-dev] [All] Finish test job transition to Ubuntu Xenial

On 18/11/2016 12:17, Jakub Libosvar wrote: On 07/11/2016 23:04, Clark Boylan wrote: On Mon, Nov 7, 2016, at 01:48 PM, Clark Boylan wrote: How can you do this? First double check your job logs to see where your tests are running. The first few lines of your job console logs should say "[Zuul]

Re: [openstack-dev] [Stable] Usefulness of Weekly Meeting

> On 16 Nov 2016, at 15:12, Matt Riedemann wrote: > > On 11/16/2016 7:53 AM, Ian Cordasco wrote: >> >> >> -Original Message- >> From: Ian Cordasco >> Reply: Ian Cordasco >> Date: November 16, 2016 at

[openstack-dev] [nova] placement/resource providers update 2

Last week I made an update[0] on the state of things in the resource provider/placement API universe. That seemed pretty useful, so here's another one. Even though most people were productively involved in reviewing specs before yesterday's deadline, some placement related specs and code merged,

Re: [openstack-dev] [kolla] Obtaining version information for Docker container

If I'm understanding the requirement correctly, we want to know which version of an OpenStack component is installed in an image? If so why not just run something like: # docker run kolla/oraclelinux-source-keystone:3.0.0 pip show keystone Name: keystone Version: 10.0.0.0rc2.dev290 [...] Or

Re: [openstack-dev] [kolla][git]How to backport commit after repo split

You mean contributing doc? Sounds like a winner to me. I am really concerned about how to sort out back ports as it relates to the repository split, and documenting a best practice here makes a lot of sense (once we figure out what that simple best practice is - which I think is covered in

[openstack-dev] [kolla] Obtaining version information for Docker container

Zhu, This isn’t the first time this question has been asked :) Since this is a technical matter, I’ve copied openstack-dev for a wider audience. I don’t have a clear solution to obtaining version manifests for container content or the upstream container version. Perhaps someone in our

Re: [openstack-dev] [All] Finish test job transition to Ubuntu Xenial

On 07/11/2016 23:04, Clark Boylan wrote: On Mon, Nov 7, 2016, at 01:48 PM, Clark Boylan wrote: How can you do this? First double check your job logs to see where your tests are running. The first few lines of your job console logs should say "[Zuul] Building remotely on ubuntu-xenial" if

Re: [openstack-dev] [neutron] rally failure in the gate

Hi stackers! Imo, there is a better solution - just turn off telemetry services[*] :) Neutron jobs do not runs any ceilometer scenarios, so enabling all telemetry services looks redundant and takes some time while preparing environment (installing devstack). [*] -

Re: [openstack-dev] [neutron] rally failure in the gate

> On 17 Nov 2016, at 20:32, Armando M. wrote: > > Hi folks, > > Please do not recheck rally failures. > > There was a breaking change introduced by aodh [0] that prevented rally to > work on trusty. We are switching to xenial as we speak anyway [1], so the > glitch should

Re: [openstack-dev] [Neutron] Stepping down from core

> On 17 Nov 2016, at 19:42, Carl Baldwin wrote: > > Neutron (and Openstack), > > It is with regret that I report that my work situation has changed such that > I'm not able to keep up with my duties as a Neutron core reviewer, L3 > lieutenant, and drivers team member. My

Re: [openstack-dev] [api]

No prob! Just needed a hint preferably before we'd merge the new API endpoint spec for the inspector [1] Cheers, milan [1] https://review.openstack.org/#/c/375045/10/specs/list-introspection-statuses.rst pá 18. 11. 2016 v 11:26 odesílatel Chris Dent napsal: > On Fri, 18

Re: [openstack-dev] [Neutron] Stepping down from core

Hi Carl, Your great work always helped Neutron community. Thank you so much for all your help. Hirofumi On 2016/11/18 3:42, Carl Baldwin wrote: Neutron (and Openstack), It is with regret that I report that my work situation has changed such that I'm not able to keep up with my duties as a

Re: [openstack-dev] [api]

On Fri, 18 Nov 2016, milanisko k wrote: Sorry Ed, was a bank holiday in here yesterday. Did the API WG conclude on a preferred operator name? After bouncing it around a few times 'nin' seemed to fit better and Ed proposed a guideline: https://review.openstack.org/#/c/399131/ Thanks

Re: [openstack-dev] [Neutron] Stepping down from core

Hi Carl, It was a pleasure working with you. All the best in your new venture. Regards, Martin From: Carl Baldwin To: OpenStack Development Mailing List Date: 17/11/2016 18:43 Subject:[openstack-dev]

Re: [openstack-dev] [Neutron] Stepping down from core

Sad to see you go Carl, Thanks for so many years of hard work, as Brian said, OpenStack / Neutron is better thanks to your contributions through the last years. My best wishes for you. On Fri, Nov 18, 2016 at 9:51 AM, Vikram Choudhary wrote: > It was really a good

Re: [openstack-dev] [api]

Sorry Ed, was a bank holiday in here yesterday. Did the API WG conclude on a preferred operator name? Cheers, milan st 16. 11. 2016 v 15:43 odesílatel Ed Leafe napsal: On Nov 16, 2016, at 7:42 AM, Ian Cordasco wrote: > If you're including me as a vote

Re: [openstack-dev] [architecture] Reminder: Arch-WG Meeting today, and -- repo

i attended the Asia friendly meeting several times but found no one was on it, is the EU one also Asia friendly ? On Fri, Nov 18, 2016 at 4:57 PM, Thierry Carrez wrote: > Clint Byrum wrote: > > Just a friendly reminder that we have a meeting today at 19:00 UTC. > > Please

Re: [openstack-dev] [architecture] Reminder: Arch-WG Meeting today, and -- repo

Clint Byrum wrote: > Just a friendly reminder that we have a meeting today at 19:00 UTC. > Please come join us and add anything you'd like to talk about to the > Agenda: > > https://wiki.openstack.org/wiki/Meetings/Arch-WG > > On another note, we have a repository now to facilitate our

Re: [openstack-dev] [Neutron] Stepping down from core

It was really a good experience working with you Carl. Best of luck for your future endeavour! Thanks Vikram On Fri, Nov 18, 2016 at 12:38 PM, Trinath Somanchi wrote: > Carl - > > > > You are an asset to Neutron community. Missing you as core is a hard > thing. > > >

Re: [openstack-dev] [Horizon] Proposing Kenji Ishii for core

+1 On Fri, Nov 18, 2016 at 12:35 AM Thai Q Tran wrote: > +1 from me. Kenji is also very active in the plugin space. > > > - Original message - > From: David Lyle > To: "OpenStack Development Mailing List (not for usage questions)" < >

[openstack-dev] [new][horizon] XStatic-JSEncrypt 2.3.1.1 release

We are frolicsome to announce the release of: XStatic-JSEncrypt 2.3.1.1: JSEncrypt 2.3.1 (XStatic packaging standard) Download the package from: https://pypi.python.org/pypi/XStatic-JSEncrypt For more details, please see below. Changes in XStatic-JSEncrypt 2.3.1.0..2.3.1.1