Re: [openstack-dev] [puppet] Request to create puppet-tacker

Yeah, super good news! Please do the same as I did in https://review.openstack.org/326720 and https://review.openstack.org/326721 Add me as reviewer because I need to sign-off the 2 patches (I'm current PTL). Once it's done & merged, you'll be able to deprecate the old repository on your github

Re: [openstack-dev] [kolla] Request for changing the meeting time to 1600 UTC for all meetings

+1 from me. But I'd love to hear from Jeffrey if he'd be ok with that too. On 8 June 2016 at 07:54, Swapnil Kulkarni (coolsvap) wrote: > Dear Kollagues, > > Some time ago we discussed the requirement of alternating meeting > times for Kolla weekly meeting due to major

Re: [openstack-dev] [kolla] Request for changing the meeting time to 1600 UTC for all meetings

+1 On 08/06/16 13:54, Swapnil Kulkarni (coolsvap) wrote: Dear Kollagues, Some time ago we discussed the requirement of alternating meeting times for Kolla weekly meeting due to major contributors from kolla-mesos were not able to attend weekly meeting at UTC 1600 and we implemented alternate

Re: [openstack-dev] [kolla] Request for changing the meeting time to 1600 UTC for all meetings

+1 2016-06-08 10:29 GMT-03:00 Jeffrey Zhang : > it will be mid-night (0:00) in my local time. But i think i am OK with it. > so +1 for this. > > On Wed, Jun 8, 2016 at 9:12 PM, Paul Bourke > wrote: > >> +1 >> >> On 08/06/16 13:54, Swapnil

Re: [openstack-dev] [kolla] OSIC cluster accepteed

Cool. Do we have any test list now? and how can i help for this? I am very interested in this test. On Tue, Jun 7, 2016 at 4:52 PM, Paul Bourke wrote: > Michal, > > I'd be interested in helping with this. Keep us updated! > > -Paul > > > On 03/06/16 17:58, Michał

Re: [openstack-dev] Got Failure:"fixtures._fixtures.timeout.TimeoutException"

On Tue, Jun 7, 2016, at 10:40 PM, zhangshuai wrote: > Hi all > > I have a question with fixtures._fixtures.timeout.TimeoutException. like > following: > > > > > Traceback (most recent call last): > > File "smaug/tests/fullstack/test_checkpoints.py", line 73, in > test_checkpoint_create >

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

John, Is the blueprint Louis posted this one? https://blueprints.launchpad.net/networking-sfc/+spec/networking-sfc-ovn-driver If not, can you send me the link? Regards, Juno Zhu IBM China Development Labs (CDL) Cloud IaaS Lab Email: na...@cn.ibm.com 5F, Building 10, 399 Keyuan Road, Zhangjiang

Re: [openstack-dev] Reasoning behind my vote on the Go topic

Samuel Merritt wrote: On 6/7/16 12:00 PM, Monty Taylor wrote: [snip] > I'd rather see us focus energy on Python3, asyncio and its pluggable event loops. The work in: http://magic.io/blog/uvloop-blazing-fast-python-networking/ is a great indication in an actual apples-to-apples comparison

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

Hi John, I think you can create ovsdb idl client in networking-sfc to connect to OVN_Northbound DB, then call the APIs you add to networking-ovn to configure SFC. Now OVN is a ML2 mechanism driver (OVNMechanismDriver), not core plugin, the OVN L3 (OVNL3RouterPlugin) is a neutron service plugin

Re: [openstack-dev] [heat][TripleO] Adding interfaces to environment files?

On Tue, Jun 07, 2016 at 04:53:12PM -0400, Zane Bitter wrote: > On 07/06/16 15:57, Jay Dobies wrote: > > > > > > 1. Now that we support passing un-merged environment files to heat, > > > it'd be > > > good to support an optional description key for environments, > > > > I've never understood why

[openstack-dev] [tricircle]agenda of weekly meeting of Jun.8

Hi, IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on every Wednesday starting from UTC 13:00. Today's agenda: # spec review and status of 'cross pod L2 networking' and 'dynamic pod binding' # policy enforcement for API access # tempest test integration If you have

[openstack-dev] [charms] Renaming openvswitch-odl -> openvswitch

Hi All The current openvswitch-odl charm is designed for use with nova-compute/neutron-gateway and the odl-controller charm, but it declares and configures OVS in such a way that I think it has broader applicability than just OpenDayLight; specifically it looks like it would also work with ONOS

Re: [openstack-dev] [Magnum] The Magnum Midcycle

Hi Hongbin. Not sure how this fits everyone, but we would be happy to host it at CERN. How do people feel about it? We can add a nice tour of the place as a bonus :) Let us know. Ricardo On Tue, Jun 7, 2016 at 10:32 PM, Hongbin Lu wrote: > Hi all, > > > > Please find

[openstack-announce] Gnocchi 2.1.2 released

Hi, We are pleased to announce the release of Gnocchi 2.1.2. This is our next micro version, fixings one bug. You can get more information about some of the bugs fixed on Launchpad: https://launchpad.net/gnocchi/2.1/2.1.2 It's also available on PyPI:

Re: [openstack-dev] [neutron] OVSDB native interface as default in gate jobs

On Tue, Apr 5, 2016, at 08:32 PM, IWAMOTO Toshihiro wrote: > At Tue, 5 Apr 2016 12:57:33 -0400, > Assaf Muller wrote: > > > > On Tue, Apr 5, 2016 at 12:35 PM, Sean M. Collins wrote: > > > Russell Bryant wrote: > > >> because they are related to two different command line

[openstack-dev] [charms] Re-licensing OpenStack charms under Apache 2.0

Hi We're currently blocked on becoming an OpenStack project under the big-tent by the licensing of the 26 OpenStack charms under GPL v3. I'm proposing that we re-license the following code repositories as Apache 2.0: charm-ceilometer charm-ceilometer-agent charm-ceph charm-ceph-mon

Re: [openstack-dev] [ironic] using ironic as a replacement for existing datacenter baremetal provisioning

On 07/06/2016 23:59, "Kris G. Lindgren" > wrote: Replying to a digest so sorry for the copy and pastes >> There's also been discussion of ways we could do ad-hoc changes in RAID >> level, >> based on flavor metadata, during the

Re: [openstack-dev] [nova][scheduler] bug in handling of ISOLATE thread policy

On 07 Jun 11:36, Chris Friesen wrote: > Hi, > > The full details are available at > https://bugs.launchpad.net/nova/+bug/1590091 but the short version > is this: > > 1) I'm running stable/mitaka in devstack. I've got a small system > with 2 pCPUs, both marked as available for pinning. They're

Re: [openstack-dev] [nova][scheduler] bug in handling of ISOLATE thread policy

On 08 Jun 10:11, Finucane, Stephen wrote: > On 07 Jun 11:36, Chris Friesen wrote: > > Hi, > > > > The full details are available at > > https://bugs.launchpad.net/nova/+bug/1590091 but the short version > > is this: > > > > 1) I'm running stable/mitaka in devstack. I've got a small system > >

Re: [openstack-dev] [heat][TripleO] Adding interfaces to environment files?

On Tue, Jun 07, 2016 at 03:57:31PM -0400, Jay Dobies wrote: > > All, > > > > We've got some requirements around adding some interfaces to the heat > > environment file format, for example: > > > > 1. Now that we support passing un-merged environment files to heat, it'd be > > good to support an

Re: [openstack-dev] [nova][glance][qa] Test plans for glance v2 stack

On 06/07/2016 04:55 PM, Matt Riedemann wrote: > I tested the glance v2 stack (glance v1 disabled) using a devstack > change here: > > https://review.openstack.org/#/c/325322/ > > Now that the changes are merged up through the base nova image proxy and > the libvirt driver, and we just have

Re: [openstack-dev] [heat][TripleO] Adding interfaces to environment files?

On Wed, Jun 8, 2016 at 11:23 AM, Steven Hardy wrote: > On Tue, Jun 07, 2016 at 04:53:12PM -0400, Zane Bitter wrote: > > On 07/06/16 15:57, Jay Dobies wrote: > > > > > > > > 1. Now that we support passing un-merged environment files to heat, > > > > it'd be > > > > good to

Re: [openstack-dev] [puppet] Request to create puppet-tacker

Awesome! You just need to follow the same process that Emilien pointed for puppet-congress. If you need any help please let us know. 1- Move https://github.com/radez/puppet-tacker to OpenStack 2- Add it to our governance 3- Follow

Re: [openstack-dev] [charms] Renaming openvswitch-odl -> openvswitch

Project renames are limited to certain maintenance windows @ infra, so that's something to be aware of re: timing and coordination. Also for clarity, can we discuss and highlight the differing use cases and eventual plans a bit re: the neutron-openvswitch subordinate charm vs. the openvswitch

Re: [openstack-dev] [magnum][heat] spawn a group of nodes on different availability zones

One more example how you may do it using yaql: oleksii@oleksii:~$ cat example.yaml heat_template_version: 2013-05-23 parameters: az_list: type: string count: type: number resources: rg: type: OS::Heat::ResourceGroup properties: count: {get_param: count}

Re: [openstack-dev] [ironic] using ironic as a replacement for existing datacenter baremetal provisioning

On Wed, Jun 08, 2016 at 10:39:20AM +, Sam Betts (sambetts) wrote: > > > On 07/06/2016 23:59, "Kris G. Lindgren" > > wrote: > > Replying to a digest so sorry for the copy and pastes > > > >> There's also been discussion of ways we

[openstack-dev] [puppet] Request to create puppet-tacker

I also have puppet-tacker module that has existed before the project was part of big tent. It was based on cookie cutter originally but will probably need some adjustments to adhere to standards. I'd like to get the project establish so that the code can be run through the proper review process.

Re: [openstack-dev] [nova][glance][qa] Test plans for glance v2 stack

On 6/8/2016 6:50 AM, Sean Dague wrote: On 06/07/2016 04:55 PM, Matt Riedemann wrote: I tested the glance v2 stack (glance v1 disabled) using a devstack change here: https://review.openstack.org/#/c/325322/ Now that the changes are merged up through the base nova image proxy and the libvirt

[openstack-dev] [Neutron] neutron-lib and dependencies in neutron reference implementation

Hello all, I have recently came across some missing constants in neutron-lib and sent a patch but i wanted to try and understand the scope of the lib. I see that the Neutron lib consist of many definitions which are actually part of the reference implementation and are not really "generic"

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

Hi John, Looking at the code with Srilatha, it seems like the https://github.com/doonhammer/networking -ovn repo has gone down the path of having a sfc_ovn.py file in the networking-ovn/ovsdb directory. This file deals with the SFC specific OVSDB

Re: [openstack-dev] [keystone]trusts with federated users

> > As an OIDC user, tried to play with Heat and Murano recently. They usually > fail with a trust creation error, noticing that keystone cannot find the > _member_ role while creating the trust. > Hmmm...that should not be the case. The user in question should have a > role on the project, but

Re: [openstack-dev] [Neutron] Getting project version from API

> This handshake between Neutron and Nova does not happen over RPC Sorry, Armando, you're absolutely right. What I meant to say is, that this communication goes via the Message Bus instead of an ReST API. Thanks for correcting! -- - Andreas IRC: andreas_s On Mo, 2016-06-06 at 20:17

Re: [openstack-dev] [Neutron] Getting project version from API

Now I'm blaming myself - had a closer look at the code - it's NOT a message via the Bus, but some nova external events interface that I was not aware of. Sorry for all the confusion -- - Andreas IRC: andreas_s On Mi, 2016-06-08 at 08:09 +0200, Andreas Scheuring wrote: > > This handshake

[openstack-dev] [VPNaaS] Support for Stronger hashes and combined mode ciphers

Hi, I was wondering if there are any plans to extend support for IPsec and IKE algorithms. Looks like only AES-CBC mode and SHA1 are supported. It would be nice to see: SHA256, SHA384, SHA512 As well as the combined mode ciphers: AES-CCM and AES-GCM StrongSWAN already supports all of

Re: [Openstack-operators] [scientific-wg] Maximise resource utilisation (was Scientific Working Group IRC meeting, Weds @0700 UTC in #openstack-meeting)

Sorry I was not able to make it. To clarify on Blazar for CERN (http://eavesdrop.openstack.org/meetings/scientific_wg/2016/scientific_wg.2016-06-08-06.59.log.html), we’re interested in the overall problem of how to maximize the utilization of the resources in the private cloud rather than a

Re: [openstack-dev] [glance] Proposal of a virtual mid-cycle instead of the co-located

This event is confirmed, more details will be out soon. On 5/29/16 11:15 PM, Nikhil Komawar wrote: > Hello, > > > I would like to propose a two day 4 hour sessions each of Glance virtual > mid-cycle on June 15th Wednesday & 16th Thursday, 1400 UTC onward. This > is a replacement of the Glance

Re: [openstack-dev] [Magnum] The Magnum Midcycle

Ricardo, Thanks for the offer. Would I know where is the exact location? Best regards, Hongbin > -Original Message- > From: Ricardo Rocha [mailto:rocha.po...@gmail.com] > Sent: June-08-16 5:43 AM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re:

Re: [OpenStack-Infra] JJB's use of inspect plugin info requires administrator permissions

On 06/08/2016 05:51 AM, Darragh Bailey wrote: --[snip]-- > > Unfortunately it's come to our attention that this feature in > Jenkins requires the Administrator permission which can be > problematic if you have an environment where you prefer not to > give this

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

Hi John, Thanks your effort, So the next plan is you submit the WIP patches, then I submit test script about your code changes, do you think it is ok? Regards, Juno Zhu IBM China Development Labs (CDL) Cloud IaaS Lab Email: na...@cn.ibm.com 5F, Building 10, 399 Keyuan Road, Zhangjiang Hi-Tech

Re: [OpenStack-Infra] Fwd: JJB 1.6.0 "Cannot create a file when that file already exists"

Hi Darragh, are you going to make that change in Gerrit? -- Sebastian Schuberth On Thu, Jun 9, 2016 at 12:52 AM, Darragh Bailey wrote: > Doh! It's called not using windows enough. > > The os.rename() it appears throws an error on windows if the target file >

[openstack-announce] [new][puppet] puppet-aodh 9.0.0 release (newton)

We are pleased to announce the release of: puppet-aodh 9.0.0: Puppet module for OpenStack Aodh This release is part of the newton release series. For more details, please see below. 9.0.0 ^ This is the first Mitaka release for puppet-aodh module. New Features * Add support

[openstack-announce] [new][puppet] puppet-keystone 9.0.0 release (newton)

We are amped to announce the release of: puppet-keystone 9.0.0: Puppet module for OpenStack Keystone This release is part of the newton release series. For more details, please see below. 9.0.0 ^ This is the first Mitaka release for puppet-keystone module. Support for multi-domain has

[openstack-announce] [new][puppet] puppet-manila 9.0.0 release (newton)

We are amped to announce the release of: puppet-manila 9.0.0: Puppet module for OpenStack Manila This release is part of the newton release series. For more details, please see below. 9.0.0 ^ This is the first Mitaka release for puppet-manila module. New Features * Add

[openstack-announce] [new][puppet] puppet-tempest 9.0.0 release (newton)

We are tickled pink to announce the release of: puppet-tempest 9.0.0: Puppet module for OpenStack Tempest This release is part of the newton release series. For more details, please see below. 9.0.0 ^ This is the first Mitaka release for puppet-tempest module. New Features

[openstack-announce] [new][puppet] puppet-trove 9.0.0 release (newton)

We are thrilled to announce the release of: puppet-trove 9.0.0: Puppet module for OpenStack Trove This release is part of the newton release series. For more details, please see below. 9.0.0 ^ This is the first Mitaka release for puppet-trove module. New Features * Add

[openstack-announce] [new][puppet] puppet-ovn 9.0.0 release (newton)

We are tickled pink to announce the release of: puppet-ovn 9.0.0: Puppet module for OVN This is the first release of puppet-ovn. This release is part of the newton release series. For more details, please see below. 9.0.0 ^ First release of puppet-ovn. Changes in puppet-ovn

Re: [openstack-dev] [neutron][upgrades] Bi-weekly upgrades work status. 6/2/2016

On Thu, Jun 2, 2016 at 2:29 PM, Korzeniewski, Artur wrote: > I would like to remind that agreed approach at Design Summit in Austin was, > that every new resource added to neutron should have OVO implemented. Please > comply, and core reviewers please take care of

Re: [openstack-dev] [ovs-discuss] [OVN] [networking-ovn] [networking-sfc] SFC andOVN

Juno, Ok added the code and I have port-chains creating up to the IDL networking-sfc->networking-ovn then I have an issue with my IDL I need to fix. So we have a model for creating port-chains all the way through, updated the repos to reflect the changes. Thanks for your help. Regards John

Re: [Openstack-operators] How are folks providing GPU instance types?

Finally circled back to this thread... Joe - those are great notes! On 12 May 2016 at 02:51, Joe Topjian wrote: > * I found that I didn't have to use EFI-based images. I wonder why that is? Yeah, we've never run into this as a requirement either. Peter - can you clarify?

Re: [openstack-dev] [zaqar][zaqar-ui] Nomating Shu Muto for Zaqar-UI core

Hi team, Thank you for nominating to Zaqar-UI core and voting to me. I'm looking forward to working with you guys more. Yours, Shu > -Original Message- > From: Fei Long Wang [mailto:feil...@catalyst.net.nz] > Sent: Wednesday, June 08, 2016 7:15 AM > To:

Re: [openstack-dev] [nova] NUMA, huge pages, and scheduling

On 06/03/2016 12:03 PM, Paul Michali wrote: Thanks for the link Tim! Right now, I have two things I'm unsure about... One is that I had 1945 huge pages left (of size 2048k) and tried to create a VM with a small flavor (2GB), which should need 1024 pages, but Nova indicated that it wasn't able

Re: [openstack-dev] [ironic] [infra] [qa] Graphs of how long jobs take?

Thanks a bunch Mikhail, this was very helpful! I've started a dashboard to track Ironic tempest job speeds as well as IPA -src job speeds; it's here; http://graphite.openstack.org/dashboard/#ironic-job-duration Please feel free to improve upon it or add additional useful metrics. Given

Re: [openstack-dev] [nova] Initial oslo.privsep conversion?

On 6/8/2016 5:51 PM, Michael Still wrote: This seems like the sort of thing we should document in the devref. I agree we shouldn't be doing any more of the old thing and should provide a worked example of the new thing. Michael -- Rackspace Australia

Re: [openstack-dev] [nova] Austin summit priorities session recap

On 6/8/2016 7:19 PM, Bias, Randy wrote: I just want to point out that this appears to imply that open source storage backends for OpenStack would be prioritized over closed-source ones and I think that runs counter to the general inclusivity in the community. I assume it¹s just a turn of

Re: [openstack-dev] Reasoning behind my vote on the Go topic

On 06/07/2016 04:26 PM, Ben Meyer wrote: On 06/07/2016 06:09 PM, Samuel Merritt wrote: On 6/7/16 12:00 PM, Monty Taylor wrote: [snip] I'd rather see us focus energy on Python3, asyncio and its pluggable event loops. The work in: http://magic.io/blog/uvloop-blazing-fast-python-networking/ is

Re: [openstack-dev] [kolla] Request for changing the meeting time to 1600 UTC for all meetings

+1 From: Mauricio Lima [mailto:mauricioli...@gmail.com] Sent: Wednesday, June 8, 2016 7:07 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [kolla] Request for changing the meeting time to 1600 UTC for all meetings +1 2016-06-08 10:29 GMT-03:00

Re: [openstack-dev] [kolla] Request for changing the meeting time to 1600 UTC for all meetings

+1 Regards, Vikram Hosakote IRC: vhosakot From: "Swapnil Kulkarni (coolsvap)" > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > Date: Wednesday,

Re: [openstack-dev] [kolla] OSIC cluster accepteed

If kolla-upgrade is in the list, I would like to help to test it. From: Vikram Hosakote (vhosakot) [mailto:vhosa...@cisco.com] Sent: Wednesday, June 8, 2016 11:18 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [kolla] OSIC cluster accepteed I'd

Re: [openstack-dev] [nova][scheduler] bug in handling of ISOLATE thread policy

On 06/07/2016 11:36 AM, Chris Friesen wrote: Hi, The full details are available at https://bugs.launchpad.net/nova/+bug/1590091 but the short version is this: 1) I'm running stable/mitaka in devstack. I've got a small system with 2 pCPUs, both marked as available for pinning. They're two

Re: [openstack-dev] [Magnum] The Magnum Midcycle

Hi Hongbin. CERN's location: https://goo.gl/maps/DWbDVjnAvJJ2 Cheers, Spyros On 8 June 2016 at 16:01, Hongbin Lu wrote: > Ricardo, > > Thanks for the offer. Would I know where is the exact location? > > Best regards, > Hongbin > > > -Original Message- > > From:

<    1   2