Re: [openstack-dev] [nova] [glance] [cinder] [neutron] - Global Request ID progress

On 06.06.2017 13:49, Sean Dague wrote: > Some good progress has been made so far on Global Request ID work in the > core IaaS layer, here is where we stand. > > STATUS > > oslo.context / oslo.middleware - everything DONE > > devstack logging additional global_request_id - DONE > > cinder: > - c

Re: [openstack-dev] [nova][neutron]Nova cells v2+Neutron+Tricircle, it works

Hello, Matt, See inline comments with [joehuang] Best Regards Chaoyi Huang (joehuang) From: Matt Riedemann [mriede...@gmail.com] Sent: 07 June 2017 10:09 To: openstack-dev@lists.openstack.org; openstack-operat...@lists.openstack.org Subject: Re: [openstac

Re: [openstack-dev] [nova] Fix an issue with resolving citations in nova-specs

On 2017/06/05 22:19, Sean Dague wrote: On 06/05/2017 01:06 AM, Takashi Natsume wrote: But IMO, it is better to fix citations in specs (*4) rather than capping the sphinx version. Thank you for the patch, I just merged *4. Thank you. It is no longer necessary to cap the sphinx version in nov

Re: [openstack-dev] [nova][neutron]Nova cells v2+Neutron+Tricircle, it works

On 5/28/2017 6:58 PM, joehuang wrote: Hello, There is one session in OpenStack Boston summit about Neutron multi-site, and discuss how to make Neutron cells-aware[1]. We have done experiment how Nova cells v2 + Neutron + Tricircle can work very well: Thanks for testing this out Joe. It's g

Re: [openstack-dev] [tc] [all] TC Report 23

On 6/6/2017 5:10 PM, Chris Dent wrote: This week had a scheduled TC meeting for the express purpose of discussing what to do about PostgreSQL. The remainder of this document has notes from that meeting. Just wanted to say thanks for the nice summary. I just got done writing up something simila

[openstack-dev] [all][infra] Missing OpenSSL headers (fatal error: openssl/opensslv.h: No such file or directory)

Greetings, If your project is seeing the following errors, this likely means you do not have libssl development headers included in your bindep.txt file. To fix this you can add the following to your local bindep.txt file: libssl-dev [platform:dpkg] openssl-devel [platform:rpm] This will en

[openstack-dev] [tc] [all] TC Report 23

This week had a TC meeting. Notes from that are in the last section below. Information about other pending or new changes that may impact readers are in the earlier sections. # New Things The TC now has [office hours](https://governance.openstack.org/tc/#office-hours) and a dedicated IRC channe

Re: [openstack-dev] [Openstack-operators] [keystone][nova][cinder][glance][neutron][horizon][policy] defining admin-ness

On Tue, Jun 6, 2017 at 4:44 PM, Lance Bragstad wrote: > > > On Tue, Jun 6, 2017 at 3:06 PM, Marc Heckmann > wrote: >> >> Hi, >> >> On Tue, 2017-06-06 at 10:09 -0500, Lance Bragstad wrote: >> >> Also, with all the people involved with this thread, I'm curious what the >> best way is to get consens

Re: [openstack-dev] [Openstack-operators] [keystone][nova][cinder][glance][neutron][horizon][policy] defining admin-ness

On Tue, Jun 6, 2017 at 3:06 PM, Marc Heckmann wrote: > Hi, > > On Tue, 2017-06-06 at 10:09 -0500, Lance Bragstad wrote: > > Also, with all the people involved with this thread, I'm curious what the > best way is to get consensus. If I've tallied the responses properly, we > have 5 in favor of opt

[openstack-dev] [nova][out-of-tree drivers] InstanceInfo/get_info getting a haircut

If you don't maintain an out-of-tree nova compute driver, you can probably hit Delete now. A proposed change [1] gets rid of some unused fields from nova.virt.hardware.InstanceInfo, which is the thing returned by ComputeDriver.get_info(). I say "unused" in the context of the nova project. If you

Re: [openstack-dev] [upgrades][skip-level][leapfrog] - RFC - Skipping releases when upgrading

On Fri, May 26, 2017 at 4:55 AM, Carter, Kevin wrote: > > Hello Stackers, > > Hi Kevin, all, apologies for the very late response here - fwiw I was working at a remote location all of last week and am catching up still. I was not at the PTG or part of the original conversation but this thread &&

Re: [openstack-dev] [tripleo] Deprecated Parameters Warning

On Tue, Jun 6, 2017 at 6:53 AM, Saravanan KR wrote: > Hello, > > I am working on a patch [1] to list the deprecated parameters of the > current plan. It depends on a heat patch[2] which provides > parameter_group support for nested stacks. The change is to add a new > workflow to analyze the plan

[openstack-dev] [MassivelyDistributed] IRC Meeting tomorrow 15:00 UTC

Dear all, A gentle reminder for our meeting tomorrow. As usual, the agenda is available at: https://etherpad.openstack.org/p/massively_distributed_ircmeetings_2017 (line 675) Please feel free to add items. Best, ad_rien_ __

[openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

Following-up the session that we had in Boston: https://etherpad.openstack.org/p/BOS-forum-future-of-configuration-management Here's an update on where we are and what is being done. == Machine Readable Sample Config Ben's spec has been merged: https://review.openstack.org/#/c/440835/ And also

Re: [openstack-dev] [reno] we need help reviewing patches to reno

Hi Doug, Will participate in reno reviews. Regards, Vikash *"Without requirements or design, programming is the art of adding bugs to an empty text file."- Louis Srygley* On Tue, Jun 6, 2017 at 8:41 PM, Julien Danjou wrote: > On Tue, Jun 06 2017, Doug Hellmann wrote: > > > I am looking f

Re: [openstack-dev] [nova] [glance] [cinder] [neutron] - Global Request ID progress

On 6 June 2017 at 04:49, Sean Dague wrote: > Some good progress has been made so far on Global Request ID work in the > core IaaS layer, here is where we stand. > > STATUS > > oslo.context / oslo.middleware - everything DONE > > devstack logging additional global_request_id - DONE > > cinder: > -

Re: [openstack-dev] KVM Forum 2017: Call For Participation

A quick reminder that the deadline for submissions to the KVM Forum 2017 is just 10 days away now, June 15. On Tue, May 09, 2017 at 01:50:52PM +0100, Daniel P. Berrange wrote: > > KVM Forum 2017: Call For Participation > October 25-2

Re: [openstack-dev] [reno] we need help reviewing patches to reno

On Tue, Jun 06 2017, Doug Hellmann wrote: > I am looking for one or two people interested in learning about how reno > works to help with reviews. If you like graph traversal algorithms > and/or text processing, have a look at the code in the openstack/reno > repository and let me know if you're i

Re: [openstack-dev] [Openstack-operators] [keystone][nova][cinder][glance][neutron][horizon][policy] defining admin-ness

Also, with all the people involved with this thread, I'm curious what the best way is to get consensus. If I've tallied the responses properly, we have 5 in favor of option #2 and 1 in favor of option #3. This week is spec freeze for keystone, so I see a slim chance of this getting committed to Pik

Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

On 06/06/2017 03:21 AM, Dougal Matthews wrote: > > > On 31 May 2017 at 09:35, Renat Akhmerov > wrote: > > > On 31 May 2017, 15:08 +0700, Thierry Carrez >, wrote: >> >>> This has hit us with the mistral and tripleo proj

Re: [openstack-dev] [Openstack-operators] [keystone][nova][cinder][glance][neutron][horizon][policy] defining admin-ness

I replied to John, but directly. I'm sending the responses I sent to him but with the intended audience on the thread. Sorry for not catching that earlier. On Fri, May 26, 2017 at 2:44 AM, John Garbutt wrote: > +1 on not forcing Operators to transition to something new twice, even if > we did g

Re: [openstack-dev] [nova][scheduler][placement] Allocating Complex Resources

On Mon, 5 Jun 2017, Ed Leafe wrote: One proposal is to essentially use the same logic in placement that was used to include that host in those matching the requirements. In other words, when it tries to allocate the amount of disk, it would determine that that host is in a shared storage aggrega

[openstack-dev] [nova] notification update week 23

Hi, After two weeks of silence here is the status update / fucus setting mail about notification work for week 23. Bugs [Medium] https://bugs.launchpad.net/nova/+bug/1657428 The instance notifications are sent with inconsistent timestamp format. One of the prerequisite patches needs som

[openstack-dev] [reno] we need help reviewing patches to reno

I am looking for one or two people interested in learning about how reno works to help with reviews. If you like graph traversal algorithms and/or text processing, have a look at the code in the openstack/reno repository and let me know if you're interested in helping out. Doug __

[openstack-dev] [kolla][tripleo][docker][containers] COW fs for docker images cache and registry, looking for solutions

Hello all. I'm researching the subject, which is 'on-line de-duplicating' the space consumed by cached docker images and pushed into a local private registry on the same host, like using fs with COW (btrfs/zfs?). There is related bug for TripleO [0]. Could you please share some ideas or perhaps so

[openstack-dev] [os-upstream-institute] Alternating meeting slot

Hi Training Team, As we have many team members from Europe and Asia we are now switching to alternating meeting slots [1] starting from next week. On even weeks our meeting slot is 0900 UTC on Tuesdays, while on odd weeks it’s 2000 UTC on Mondays, all on #openstack-meeting-3. Our meeting next

Re: [openstack-dev] [nova][scheduler][placement] Allocating Complex Resources

Le 06/06/2017 15:03, Edward Leafe a écrit : > On Jun 6, 2017, at 4:14 AM, Sylvain Bauza > wrote: >> >> The Plan A option you mention hides the complexity of the >> shared/non-shared logic but to the price that it would make scheduling >> decisions on those criteries imp

Re: [openstack-dev] [nova][scheduler][placement] Allocating Complex Resources

On Jun 6, 2017, at 4:14 AM, Sylvain Bauza wrote: > > The Plan A option you mention hides the complexity of the > shared/non-shared logic but to the price that it would make scheduling > decisions on those criteries impossible unless you put > filtering/weighting logic into Placement, which AFAIK

Re: [openstack-dev] [tripleo] Future of the tripleo-quickstart-utils project

On 17/05/2017 10:47, Bogdan Dobrelya wrote: [...]> It is amusing a little bit as it looks a controversial to the > "Validations before upgrades and updates" effort. Shall we just move the > tripleo-quickstart-utils back to extras, or to validations repo and have > both issues solved? :) The reason

Re: [openstack-dev] [tripleo] Future of the tripleo-quickstart-utils project

On 17/05/2017 04:01, Emilien Macchi wrote: > Hey Raoul, > Thanks for putting this up in the ML. Replying inline: Sorry for the long delay between the answers, a lot of things on going. [...] > I've looked at > https://github.com/redhat-openstack/tripleo-quickstart-utils/blob/master/roles/validat

Re: [openstack-dev] [nova] [Pycharm] Pycharm Debugging

Missing title > Il giorno 06 giu 2017, alle ore 13:55, Giuseppe Di Lena > ha scritto: > > Hello guys, > are some of you using PyCharm to debugging and testing nova? > > I've cloned the Nova Project in my PC, and I want to run some unit tests with > the debugger. > I searched in these days, but

[openstack-dev] [nova] [Pycharm]

Hello guys, are some of you using PyCharm to debugging and testing nova? I've cloned the Nova Project in my PC, and I want to run some unit tests with the debugger. I searched in these days, but I found nothing. Do you have some suggestions? Best regards Giuseppe ___

[openstack-dev] [nova] [glance] [cinder] [neutron] - Global Request ID progress

Some good progress has been made so far on Global Request ID work in the core IaaS layer, here is where we stand. STATUS oslo.context / oslo.middleware - everything DONE devstack logging additional global_request_id - DONE cinder: - client supports global_request_id - DONE - Cinder calls Nova w

Re: [openstack-dev] [nova][vlan trunking] Guest networking configuration for vlan trunk

Hi Robert, I'm late to this thread, but let me add a bit. There was an attempt for trunk support in nova metadata on the Pike PTG: https://review.openstack.org/399076 But that was abandoned right after the PTG, because the agreement seemed to be in favor of putting the trunk details into the upc

Re: [openstack-dev] [TripleO] overcloud containers patches todo

On 5.6.2017 23:52, Dan Prince wrote: On Mon, 2017-06-05 at 16:11 +0200, Jiří Stránský wrote: On 5.6.2017 08:59, Sagi Shnaidman wrote: Hi I think a "deep dive" about containers in TripleO and some helpful documentation would help a lot for valuable reviews of these container patches. The knowled

Re: [openstack-dev] [tc] revised Postgresql deprecation patch for governance

For people who have been following this topic, a reminder that later today there will be a TC meeting dedicated to discussing this issues captured by this thread[1], the related thread on active or passive database approaches[2] and the two reviews about "what to do about postgreSQL" [3][4]. It

Re: [openstack-dev] [nova][scheduler][placement] Allocating Complex Resources

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Le 05/06/2017 23:22, Ed Leafe a écrit : > We had a very lively discussion this morning during the Scheduler > subteam meeting, which was continued in a Google hangout. The > subject was how to handle claiming resources when the Resource > Provider

Re: [openstack-dev] [requirements][mistral][tripleo][horizon][nova][releases] release models for projects tracked in global-requirements.txt

On 31 May 2017 at 09:35, Renat Akhmerov wrote: > > On 31 May 2017, 15:08 +0700, Thierry Carrez , > wrote: > > > This has hit us with the mistral and tripleo projects particularly > (tagged in the title). They disallow pbr-3.0.0 and in the case of > mistral sqlalchemy updates. > > [mistral] > mist