Re: [openstack-dev] [Ironic][Nova][Neutron] Multi-tenancy support

Hello Sean, Jim, Thanks for your comments. I've created separate repo: https://github.com/jumpojoy/generic_switch -- Sincerely Vasyl Saienko On Tue, Nov 17, 2015 at 1:38 AM, Jim Rollenhagen wrote: > On Mon, Nov 16, 2015 at 06:38:28PM +, Sean M. Collins wrote: > >

[openstack-dev] [oslo][All] Make CONF.set_override with paramter enforce_type=True by default

Hi ALL, 1. Problems : oslo_config provides method CONF.set_override[1] , developers usually use it to change config option's value in tests. That's convenient . By default parameter enforce_type=False, it doesn't check any type or value of override. If set enforce_type=True , will check

Re: [openstack-dev] [tripleo] Location of TripleO REST API

On 10 November 2015 at 15:08, Tzu-Mainn Chen wrote: > Hi all, > > At the last IRC meeting it was agreed that the new TripleO REST API > should forgo the Tuskar name, and simply be called... the TripleO > API. There's one more point of discussion: where should the API >

Re: [openstack-dev] [OpenStack-Infra] Report from Gerrit User Summit

On 11/17/2015 06:11 AM, David Pursehouse wrote: > On Tue, Nov 10, 2015 at 9:53 PM Sean Dague > wrote: > <...> > > > Is there any update on label:Code-Review<=-1,group:nova-core ? The group > search support is documented, but as far as I can tell

Re: [openstack-dev] [OpenStack-Infra] Report from Gerrit User Summit

On Tue, Nov 10, 2015 at 9:53 PM Sean Dague wrote: <...> > > Is there any update on label:Code-Review<=-1,group:nova-core ? The group > search support is documented, but as far as I can tell doesn't work > except under very specific ldap configs. >

Re: [openstack-dev] [networking-ovs-dpdk]

Can you provide the ovs-vswitchd log form ${OVS_LOG_DIR}/ovs-vswitchd.log /tmp/ovs-vswitchd.log in your case. If the vswitch fails to start we clean up by unmounting the hugepages. From: Prathyusha Guduri [mailto:prathyushaconne...@gmail.com] Sent: Tuesday, November 17, 2015 7:37 AM To:

Re: [openstack-dev] [nova][libvirt] Native AIO mode - RFC

On Tue, 17 Nov 2015 11:14:29 +0100 Alexander Schmidt wrote: > Hi all, > > I started a blueprint [1] and spec [2] for enabling the usage > of native AIO mode for disk devices. The idea is to enable it > for storage backends/setups where IO performance benefits from >

Re: [openstack-dev] [aodh] HBase gate job

On Tue, Nov 17 2015, ZhiQiang Fan wrote: > I prefer to deprecate all drivers except sql, but the upgrade issue > requires us providing some tools to migrate those existent data It does not require us anything if nobody steps us to do it. :) -- Julien Danjou ;; Free Software hacker ;;

[openstack-dev] [openstack-infra] Adding new members to new vitrage-dashboard-core group in gerrit is disabled

Hello, Two questions regarding new project init: 1) A new change, https://review.openstack.org/#/c/245671/, was merged earlier. In the change, I created a new gerrit group - vitrage-dashboard–core. When I open gerrit UI – I don’t see myself in the list, and I cannot add anyone as the option to

Re: [openstack-dev] [networking-ovs-dpdk]

Here is stack.sh log - 2015-11-17 13:38:50.010 | Loading uio module 2015-11-17 13:38:50.028 | Loading DPDK UIO module 2015-11-17 13:38:50.038 | starting ovs db 2015-11-17 13:38:50.038 | binding nics 2015-11-17 13:38:50.039 | starting vswitchd 2015-11-17 13:38:50.190 | sudo

Re: [openstack-dev] [aodh] HBase gate job

let's change this gate to experimental for now. On 17/11/15 05:10 AM, Julien Danjou wrote: Hi, So we recently decided to run the functional tests for the HBase driver and enabled the gate job. It turned out the gate job didn't worked, so I tried to fix it. Now it's almost fixed, and it run the

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

A quick reminder: the first live migration subteam IRC meeting is today at 1400 UTC on #openstack-meeting-3. See: https://wiki.openstack.org/wiki/Meetings/NovaLiveMigration Regards, Paul Paul Murray Nova Technical Lead, HPE Cloud Hewlett Packard Enterprise +44 117 316 2527

Re: [openstack-dev] [networking-ovs-dpdk]

Hi Sean, Here is ovs-vswitchd.log 2015-11-13T12:48:01Z|1|dpdk|INFO|User-provided -vhost_sock_dir in use: /var/run/openvswitch EAL: Detected lcore 0 as core 0 on socket 0 EAL: Detected lcore 1 as core 1 on socket 0 EAL: Detected lcore 2 as core 2 on socket 0 EAL: Detected lcore 3 as core 3 on

Re: [openstack-dev] [oslo][All] Make CONF.set_override with paramter enforce_type=True by default

+1 to what Doug said. Thanks ChangBo! -- dims On Tue, Nov 17, 2015 at 10:47 AM, Doug Hellmann wrote: > Excerpts from ChangBo Guo's message of 2015-11-17 20:29:53 +0800: >> Hi ALL, >> >> 1. Problems : >>oslo_config provides method CONF.set_override[1] , developers

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

> https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20151117 > > <https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20151117> ? > Thanks o/ > > > 2015-11-16 14:04 GMT-03:00 Emilien Macchi <emilien.mac...@gmail.com > &l

Re: [openstack-dev] [Fuel] HA cluster disk monitoring, failover and recovery

On 17.11.2015 15:28, Kyrylo Galanov wrote: > Hi Team, Hello > > I have been testing fail-over after free disk space is less than 512 mb. > (https://review.openstack.org/#/c/240951/) > Affected node is stopped correctly and services migrate to a healthy node. > > However, after free disk space

Re: [openstack-dev] Troubleshooting cross-project comms

Sean Dague writes: > Has anyone considered using #openstack-dev, instead of a new meeting > room? #openstack-dev is mostly a ghost town at this point, and deciding > that instead it would be the dedicated cross project space, including > meetings support, might be interesting. I

Re: [openstack-dev] Troubleshooting cross-project comms

James E. Blair wrote: > Is the idea to try to re-invigorate the -dev channel > by holding meetings there? Right, that was one beneficial side-effect that I expected out of recycling #openstack-dev. Reinvigorate it through regular discussions. It also happens to have the most people joined to it

Re: [openstack-dev] [puppet] weekly meeting #58 and next week

Just for the record, here are the meeting notes: http://eavesdrop.openstack.org/meetings/puppet_openstack/2015/puppet_openstack.2015-11-10-15.00.html Thanks! On 11/08/2015 10:08 PM, Matt Fischer wrote: > We have a very light schedule if anyone would like to discuss bugs or > other issues, it

Re: [openstack-dev] [Fuel] HA cluster disk monitoring, failover and recovery

On Tue, Nov 17, 2015 at 9:01 AM, Vladimir Kuklin wrote: > Folks > > Is not it possible for an OCF script to clear this attribute after a > sufficient period of successful monitoring of node health? It could be a > better approach in this case then restarting the node. > So

Re: [openstack-dev] [Ironic] [OSC] Quick poll: OpenStackClient command for provision action

On Tue, Nov 10, 2015 at 12:19:08PM +, Sam Betts (sambetts) wrote: > So you would end up with a set of commands that look like this: After reading through this thread, I think this is mostly good, other than some word choices. I've changed a few inline to feel more natural (IMHO of course). :)

Re: [openstack-dev] [oslo][All] Make CONF.set_override with paramter enforce_type=True by default

Excerpts from ChangBo Guo's message of 2015-11-17 20:29:53 +0800: > Hi ALL, > > 1. Problems : >oslo_config provides method CONF.set_override[1] , developers usually > use it to change config option's value in tests. That's convenient . >By default parameter enforce_type=False, it

Re: [openstack-dev] [aodh] HBase gate job

On Tue, Nov 17 2015, Nadya Shakhat wrote: > Sorry I missed the letter. I'll take a look on this. As I understand, it's > enough just to run functional tests to see the issue, right? Yes, with my patch it should be pretty easy to reproduce. -- Julien Danjou -- Free Software hacker --

Re: [openstack-dev] [Fuel] Running Fuel node as non-superuser

Stanislaw, do you mean the whole feature, or just a user? Since feature would require actually changing puppet code. On Tue, Nov 17, 2015 at 5:08 AM, Stanislaw Bogatkin wrote: > Dmitry, I believe it should be done via package spec as a part of > installation. > > On Mon,

[openstack-dev] [Manila] Attach/detach semantics

Hi all, As you may know, there is ongoing work on a spec for Nova to define an "attach/detach" API for tighter integration with Manila. The concept here is that this mechanism will be needed to implement hypervisor mediated FS access using vsock, but that the mechanism should also be applicable

[openstack-dev] [all] Skipping cross-project meeting today

Hi everyone, Since Everett can't really make the cross-project meeting today, we don't have anything on the agenda to discuss. We'll therefore skip the meeting later today, although a bunch of us will be around on #openstack-meeting at that time and we can have an informal discussion if anyone

Re: [openstack-dev] [tripleo] Location of TripleO REST API

- Original Message - > On 10 November 2015 at 15:08, Tzu-Mainn Chen < tzuma...@redhat.com > wrote: > > Hi all, > > > At the last IRC meeting it was agreed that the new TripleO REST API > > > should forgo the Tuskar name, and simply be called... the TripleO > > > API. There's one more

Re: [openstack-dev] [aodh] HBase gate job

Hi folks, Sorry I missed the letter. I'll take a look on this. As I understand, it's enough just to run functional tests to see the issue, right? Nadya On Tue, Nov 17, 2015 at 4:48 PM, gord chung wrote: > let's change this gate to experimental for now. > > On 17/11/15 05:10 AM,

[openstack-dev] [mistral] Notifier about changes in the dsvm gates structure

Hello Everyone, This is a notifier about the fact that Mistral team is on the way of refactoring of current Jenkins dsvm gates infrastructure. The final goal is to have voting dsvm gates which will run on every commit to mistral and mistralclient repositories. What we have now: - mistral

Re: [openstack-dev] [Fuel] HA cluster disk monitoring, failover and recovery

Hey Kyrylo, On Tue, Nov 17, 2015 at 8:28 AM, Kyrylo Galanov wrote: > Hi Team, > > I have been testing fail-over after free disk space is less than 512 mb. > (https://review.openstack.org/#/c/240951/) > Affected node is stopped correctly and services migrate to a healthy

[openstack-dev] [Fuel] HA cluster disk monitoring, failover and recovery

Hi Team, I have been testing fail-over after free disk space is less than 512 mb. ( https://review.openstack.org/#/c/240951/) Affected node is stopped correctly and services migrate to a healthy node. However, after free disk space is more than 512 mb again the node does not recover it's state

Re: [openstack-dev] [networking-ovs-dpdk]

We mainly test with 2M hugepages not 1G however our ci does use 1G pages. We recently noticed a different but unrelated related issue with using the ivshmem target when building dpdk. (https://bugs.launchpad.net/networking-ovs-dpdk/+bug/1517032) Instead of modifying dpdk can you try Changing the

[openstack-dev] [Heat]

Hello Heat team, I recently proposed a patch https://review.openstack.org/#/c/246481/ which changes some events when resources are signaled. I was wondering if anyone has any downstream services that depend on the events being in the format specified, since this patch would break that

Re: [openstack-dev] [oslo][All] Make CONF.set_override with paramter enforce_type=True by default

ChangBo Guo wrote on 11/17/2015 01:29:53 PM: > From: ChangBo Guo > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 11/17/2015 01:37 PM > Subject: [openstack-dev] [oslo][All] Make

[openstack-dev] [oslo] [nova] default-next-release opt flag

Often in Nova we introduce an option defaulted off (so as not to break people) but then we want to make it default in the next release. Someone suggested an opt flag to mark this but I don't know what impact they wanted it to have. IE how the user should be alerted about the presence of these

[openstack-dev] [openstack-ansible] Mitaka Summit Summary

Hi everyone, I've put together some thoughts based on the Mitaka Summit from the OpenStack-Ansible point of view: http://odyssey4me.github.io/openstack/ansible/mitaka/summit/2015/11/17/mitaka-summit.html Please feel free to ping me with any feedback! Thanks, -- Jesse Pretorius IRC: odyssey4me

Re: [openstack-dev] [Fuel] HA cluster disk monitoring, failover and recovery

Bogdan I think we should firstly check whether attribute deletion leads to node starting its services or not. From what I read in the official Pacemaker documentation, it should work out of the box without the need to restart the node. And by the way the quote above mentions 'use ONE of the

Re: [openstack-dev] [glance] [nova] Image Signature Verification

On 13/11/15 09:35 +, Daniel P. Berrange wrote: On Thu, Nov 12, 2015 at 08:30:53PM +, Poulos, Brianna L. wrote: Hello, There has recently been additional discussion about the best way to handle image signature verification in glance and nova [1]. There are two options being discussed

Re: [openstack-dev] [keystone] Case for renewability of tokens, increasing expiration time

On Tuesday, November 17, 2015, Lindsay Pallickal wrote: > I was having an issue extending the expiration on unscoped and > tenant/project scoped tokens retrieved with an existing token. I now > realize this is a feature, not a bug, but I've got some points to argue > that

Re: [openstack-dev] [Fuel] Running Fuel node as non-superuser

Dmitry, I believe it should be done via package spec as a part of installation. On Mon, Nov 16, 2015 at 8:04 PM, Dmitry Nikishov wrote: > Hello folks, > > I have updated the spec, please review and share your thoughts on it: > https://review.openstack.org/#/c/243340/ > >

Re: [openstack-dev] [aodh] HBase gate job

I prefer to deprecate all drivers except sql, but the upgrade issue requires us providing some tools to migrate those existent data On Tue, Nov 17, 2015 at 6:10 PM, Julien Danjou wrote: > Hi, > > So we recently decided to run the functional tests for the HBase driver > and

Re: [openstack-dev] [Openstack-operators] Mirantis Fuel Multi-Region

Hi Folks Let me comment on a couple of things. Multiregion support is possible from deployment side. You need to pass a region parameter to corresponding nodes being deployed. It is a part of detached services feature which is delivered through plugins: "

Re: [openstack-dev] [tripleo] Location of TripleO REST API

On 10 November 2015 at 16:12, Giulio Fidente wrote: > On 11/10/2015 04:47 PM, Dmitry Tantsur wrote: > >> On 11/10/2015 04:37 PM, Giulio Fidente wrote: >> >>> On 11/10/2015 04:16 PM, Dmitry Tantsur wrote: >>> On 11/10/2015 04:08 PM, Tzu-Mainn Chen wrote: > Hi

Re: [openstack-dev] [OpenStack-Infra] Report from Gerrit User Summit

Sean Dague writes: > Given that it's on track for getting accepted upstream, it's probably > something we could cherry pick into our deploy, as it won't be a > divergence issue. Once it merges upstream, yes. -Jim

Re: [openstack-dev] [Heat]

On Tue, Nov 17, 2015 at 05:09:16PM +, Pratik Mallya wrote: >Hello Heat team, >I recently proposed a patch https://review.openstack.org/#/c/246481/ which >changes some events when resources are signaled. I was wondering if anyone >has any downstream services that depend on the

Re: [openstack-dev] [glance] [nova] Image Signature Verification

On Tue, Nov 17, 2015 at 02:09:42PM -0300, Flavio Percoco wrote: > On 13/11/15 09:35 +, Daniel P. Berrange wrote: > >On Thu, Nov 12, 2015 at 08:30:53PM +, Poulos, Brianna L. wrote: > >>Hello, > >> > >>There has recently been additional discussion about the best way to handle > >>image

Re: [openstack-dev] [oslo] [nova] default-next-release opt flag

Excerpts from Alexis Lee's message of 2015-11-17 09:28:31 -0800: > Often in Nova we introduce an option defaulted off (so as not to break > people) but then we want to make it default in the next release. > > Someone suggested an opt flag to mark this but I don't know what impact > they wanted it

Re: [openstack-dev] [Fuel] HA cluster disk monitoring, failover and recovery

On Tue, Nov 17, 2015 at 11:12 AM, Vladimir Kuklin wrote: > Bogdan > > I think we should firstly check whether attribute deletion leads to node > starting its services or not. From what I read in the official Pacemaker > documentation, it should work out of the box without

Re: [openstack-dev] [glance] [nova] Image Signature Verification

On 17/11/15 17:44 +, Daniel P. Berrange wrote: On Tue, Nov 17, 2015 at 02:09:42PM -0300, Flavio Percoco wrote: On 13/11/15 09:35 +, Daniel P. Berrange wrote: >On Thu, Nov 12, 2015 at 08:30:53PM +, Poulos, Brianna L. wrote: >>Hello, >> >>There has recently been additional discussion

Re: [openstack-dev] [stable] Preparing 2014.2.4 (Juno) WAS Re: [Openstack-operators] [stable][all] Keeping Juno "alive" for longer.

On 17/11/15 13:38, Alan Pevec wrote: 2015-11-12 21:37 GMT+01:00 Zane Bitter : https://review.openstack.org/#/q/status:open+project:openstack/heat+branch:stable/juno,n,z It would be nice to treat the remaining 'High' priority one as a blocker. The rest aren't a blocker for

[openstack-dev] [keystone][stable] nominating lin hua cheng for keystone-stable-maint

I'd like to nominate Lin Hua Cheng for keystone-stable-maint. He has been doing reviews on keystone's liberty and kilo stable branches since mitaka development has opened, and being a member of horizon-stable-maint, he is already familiar with stable branch policies. If there are no objections

Re: [openstack-dev] [nova][infra] Getting a bleeding edge libvirt gate job running

On 11/17/2015 11:10 AM, Markus Zoeller wrote: Background == The blueprint [1] wants to utilize the *virtlogd* logging deamon from libvirt. Among others to solve bug [2], one of our oldest ones. The funny part is, that this libvirt feature is still in development. This was a trigger to

Re: [openstack-dev] [nova][infra] Getting a bleeding edge libvirt gate job running

On 11/18/2015 06:10 AM, Markus Zoeller wrote: This was a trigger to see if we can create a gate job which utilizes the latest, bleeding edge, version of libvirt to test such features. * Is already someone working on something like that and I missed it? I believe the closest we have got is

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

Emilien Macchi wrote: > We did our meeting: > http://eavesdrop.openstack.org/meetings/puppet_openstack/2015/puppet_openstack.2015-11-17-15.00.html > Now that updates to the wiki doc "Coding_style" are happening, are we going to block patches that are already proposed that use the old "" pattern?

Re: [openstack-dev] [keystone] Case for renewability of tokens, increasing expiration time

On Tue, Nov 17, 2015 at 5:31 AM, Dolph Mathews wrote: > > > On Tuesday, November 17, 2015, Lindsay Pallickal > wrote: > >> >> It looks like expiration is done this way to limit the damage from stolen >> tokens, but if a token were stolen, it could

Re: [openstack-dev] [Ironic] [OSC] Quick poll: OpenStackClient command for provision action

Thanks for the list, Sam. I've left some comments inline... On Tue, Nov 10, 2015 at 4:19 AM, Sam Betts (sambetts) wrote: > So you would end up with a set of commands that look like this: > > Openstack baremetal [node/driver/chassis] list > will this command support

Re: [openstack-dev] [QA][Tempest] Deprecate or drop about Tempest CLI

On Tue, Nov 17, 2015 at 01:39:34AM +, Masayuki Igawa wrote: > Hi tempest CLI users and developers, > > Now, we are improving Tempest CLI as we discussed at the summit[1] and > migrating legacy commands to tempest cli[2]. > > In this situation, my concern is 'CLI compatibility'. > If we'll

[openstack-dev] [nova][infra] Getting a bleeding edge libvirt gate job running

Background == The blueprint [1] wants to utilize the *virtlogd* logging deamon from libvirt. Among others to solve bug [2], one of our oldest ones. The funny part is, that this libvirt feature is still in development. This was a trigger to see if we can create a gate job which utilizes the

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

Hi Cody, If there is patches using $::os_service_default and they are blocked, I think the owner just need to request removal and continue the work.( I think ) 2015-11-17 17:10 GMT-03:00 Cody Herriges : > Emilien Macchi wrote: > > We did our meeting: > > >

Re: [openstack-dev] [magnum] Autoscaling both clusters and containers

Hi Ryan, There was a talk in the last Summit on this topics to explore the options with Magnum, Senlin, Heat, Kubernetes: https://www.openstack.org/summit/tokyo-2015/videos/presentation/exploring-magnum-and-senlin-integration-for-autoscaling-containers A demo was shown with Senlin

[openstack-dev] [nfv][telco][product] Future of telco working group and weekly meeting reminder

Hi all, Back in Vancouver [1] we began discussing the growing overlap between OPNFV requirements projects and the current mission of the telco working group. During this period the product working group, also in part focused on recording and prioritizing user stories, has also been hitting its

Re: [openstack-dev] [nova] nova-manage db archive_deleted_rows broken

On 10/9/2015 1:16 PM, Matt Riedemann wrote: On 10/9/2015 12:03 PM, Jay Pipes wrote: On 10/07/2015 11:04 AM, Matt Riedemann wrote: I'm wondering why we don't reverse sort the tables using the sqlalchemy metadata object before processing the tables for delete? That's the same thing I did in

Re: [openstack-dev] [magnum] Autoscaling both clusters and containers

Ryan I haven’t seen any proposals/implementations from Mesos/Swarm (but I am not following Mesos and Swam community very close these days). But Kubernetes 1.1 has pod autoscaling (https://github.com/kubernetes/kubernetes/blob/master/docs/design/horizontal-pod-autoscaler.md), which should cover

Re: [openstack-dev] [magnum] Autoscaling both clusters and containers

It's great that we discuss this in mail list, I filed a bp here https://blueprints.launchpad.net/magnum/+spec/two-level-auto-scaling and planning a spec for this. You can get some early ideas from what Ton pointed here:

[openstack-dev] [trove] trove unit tests failing on stable/kilo

I noticed this failing today: http://logs.openstack.org/81/206681/3/check/gate-trove-python27/45d645d/console.html#_2015-11-17_17_07_28_061 Looks like https://review.openstack.org/#/c/218701/ and maybe the dependent python-troveclient change would need to be backported to stable/kilo (neither

Re: [openstack-dev] [nova] nova-manage db archive_deleted_rows broken

On 11/17/2015 05:43 PM, Matt Riedemann wrote: I found some time to work on a reverse sort of nova's tables for the db archive command, that looks like [1]. It works fine in the unit tests, but fails because the deleted instances are referenced by instance_actions that aren't deleted. I see any

Re: [openstack-dev] [Manila] Attach/detach semantics

On 11/17/2015 10:02 AM, John Spray wrote: Hi all, As you may know, there is ongoing work on a spec for Nova to define an "attach/detach" API for tighter integration with Manila. The concept here is that this mechanism will be needed to implement hypervisor mediated FS access using vsock, but

Re: [openstack-dev] [trove] trove unit tests failing on stable/kilo

On 11/17/2015 9:22 PM, Matt Riedemann wrote: I noticed this failing today: http://logs.openstack.org/81/206681/3/check/gate-trove-python27/45d645d/console.html#_2015-11-17_17_07_28_061 Looks like https://review.openstack.org/#/c/218701/ and maybe the dependent python-troveclient change

Re: [openstack-dev] [trove] trove unit tests failing on stable/kilo

On 11/17/2015 9:27 PM, Matt Riedemann wrote: On 11/17/2015 9:22 PM, Matt Riedemann wrote: I noticed this failing today: http://logs.openstack.org/81/206681/3/check/gate-trove-python27/45d645d/console.html#_2015-11-17_17_07_28_061 Looks like https://review.openstack.org/#/c/218701/ and

Re: [openstack-dev] Is latest PyCharm license still available?

The PyCharm licences are available for OpenStack developers, please send me your lauchpad-id off-list, I will help you with the updated link. Thanks Best Regards, Swapnil Kulkarni irc : coolsvap On Tue, Nov 17, 2015 at 10:06 PM, OpenStack Mailing List Archive < cor...@gmail.com> wrote: > Link:

Re: [openstack-dev] [nova] nova-manage db archive_deleted_rows broken

On 11/17/2015 7:43 PM, Matt Riedemann wrote: On 10/9/2015 1:16 PM, Matt Riedemann wrote: On 10/9/2015 12:03 PM, Jay Pipes wrote: On 10/07/2015 11:04 AM, Matt Riedemann wrote: I'm wondering why we don't reverse sort the tables using the sqlalchemy metadata object before processing the

Re: [openstack-dev] [Neutron][ThirdPartyCI] Running third party CI on networking-foo projects

hi, On Wed, Nov 18, 2015 at 2:00 AM, Fawad Khaliq wrote: > Folks, > > What would be the mechanism to enable a third party CI on a Neutron > sub-project? I am not sure if anyone has already tried it. networking-ofagent has its third party CI running. you can ask kakuma for

Re: [openstack-dev] [trove] trove unit tests failing on stable/kilo

Thanks for putting up that fix Matt. The dependency on trunk python-troveclient (for stable/kilo) definitely seems screwy-- but I'm wondering if this was done for backwards compatibility reasons? (i.e. to ensure the latest version of python-troveclient should be able to work correctly against all

Re: [openstack-dev] [openstack-infra] Vitrage is missing in the formal OpenStack launchpad

Hi Maty, Have you set up the launchpad project? http://docs.openstack.org/infra/manual/creators.html#set-up-launchpad Regards, Emma From: GROSZ, Maty (Maty) [mailto:maty.gr...@alcatel-lucent.com] Sent: Tuesday, November 17, 2015 8:18 AM To: OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [All] Use of self signed certs in endpoints

> On 16 Nov 2015, at 11:54, Sean Dague wrote: > That sounds pretty reasonable to me. I definitely support the idea that > we should be using system CA by default, even if that means overriding > requests in our tools. Setting REQUESTS_CA_BUNDLE is absolutely the way to go about

Re: [openstack-dev] [openstack-infra] Vitrage is missing in the formal OpenStack launchpad

Thanks, found what was missing… Yet another question: How does the “Series and milestones” section and "Development focus:” in launchpad is updated? I only see “trunk” and “trunk series” instead of mitake/ and mitaka series. Thanks From: "Foley, Emma L" Reply-To: "OpenStack Development

Re: [openstack-dev] [Openstack-operators] Mirantis Fuel Multi-Region

+ openstack-dev mailing list to bring more Fuel audience. On Tue, Nov 17, 2015 at 12:44 PM, Federico Michele Facca < federico.fa...@create-net.org> wrote: > Hi, > as said, you need to do manual changes to your deployed nodes. > then you will have to: > - synch your galera cluster across the two

[openstack-dev] [ceilometer][aodh][vitrage] Vitrage project

Hi Ceilometer/AODH developers, As you might have heard in Mitaka Summit, we have started a new project named Vitrage[1]. We would like it to be the Openstack RCA (Root Cause Analysis) Engine for organizing, analyzing and expanding OpenStack alarms & events, yielding insights regarding the root

[openstack-dev] [vitrage] Next vitrage meeting

Hi, Vitrage next weekly meeting will be tomorrow, Wednesday at 9:00 UTC, on #openstack-meeting-3 channel. Agenda: * Current status and progress from last week * Review action items * Next steps * Open Discussion You are welcome to join. Thanks, Ifat.

[openstack-dev] [nova][libvirt] Native AIO mode - RFC

Hi all, I started a blueprint [1] and spec [2] for enabling the usage of native AIO mode for disk devices. The idea is to enable it for storage backends/setups where IO performance benefits from using native AIO mode and where no downsides are known wrt stability or data integrity. As there is a

Re: [openstack-dev] [murano]How to use Murano to transmit files to Mistral and execute scripts on Mistral

Alexander, Thanks for your response. During the workflow running stage, it may need to access some other artifacts. In my case, I use Mistral workflow to call Ansible playbook, and I need Murano to put Ansible playbook into right place on Mistral server so that Mistral workflow can find it.

Re: [openstack-dev] [murano]How to use Murano to transmit files to Mistral and execute scripts on Mistral

Hi Tony, Probably I am missing something, but why do you need Murano Agent to interact with Mistral? You can call Mistral APIs right from MuranoPL code being executed by Murano Engine. Murano's core library contains the io.murano.system.MistralClient class ([1]) which may be used to upload and

[openstack-dev] [aodh] HBase gate job

Hi, So we recently decided to run the functional tests for the HBase driver and enabled the gate job. It turned out the gate job didn't worked, so I tried to fix it. Now it's almost fixed, and it run the functional tests and Gabbi tests against Aodh with HBase as a back-end:

[openstack-dev] [ec2api] stable/liberty release?

We are planning to cut liberty release and kilo update this or next week. (Because we are waiting a response for one small issue.) -- Kind regards, Andrey Pavlov. __ OpenStack Development Mailing List (not for usage

[openstack-dev] [Monasca][vitrage] Vitrage project

Hi Monasca developers, As you might have heard in Mitaka Summit, we have started a new project named Vitrage[1]. We would like it to be the Openstack RCA (Root Cause Analysis) Engine for organizing, analyzing and expanding OpenStack alarms & events, yielding insights regarding the root cause

[openstack-dev] [openstack-infra] Vitrage is missing in the formal OpenStack launchpad

Hello, I have lately added the new Vitrage RCA project for OpenStack. I have followed the instructions for adding a setting a new project, but for some reason, when I enters OpenStack launchpad - https://launchpad.net/openstack I don’t see the Vitrage project in the lists (for example, I don’t

Re: [openstack-dev] [oslo] [nova] default-next-release opt flag

On 11/17/2015 01:48 PM, Matt Riedemann wrote: > > > On 11/17/2015 11:28 AM, Alexis Lee wrote: >> Often in Nova we introduce an option defaulted off (so as not to break >> people) but then we want to make it default in the next release. >> >> Someone suggested an opt flag to mark this but I don't

Re: [openstack-dev] [oslo] [nova] default-next-release opt flag

Le 17/11/2015 20:25, Sean Dague a écrit : On 11/17/2015 01:48 PM, Matt Riedemann wrote: On 11/17/2015 11:28 AM, Alexis Lee wrote: Often in Nova we introduce an option defaulted off (so as not to break people) but then we want to make it default in the next release. Someone suggested an opt

Re: [openstack-dev] [openstack-infra] Adding new members to new vitrage-dashboard-core group in gerrit is disabled

On Tue, Nov 17, 2015 at 5:17 AM, GROSZ, Maty (Maty) wrote: > Two questions regarding new project init: > > 1) A new change, https://review.openstack.org/#/c/245671/, was merged > earlier. > In the change, I created a new gerrit group - vitrage-dashboard–core. > When

Re: [openstack-dev] [oslo] [nova] default-next-release opt flag

On 11/17/2015 2:05 PM, Sylvain Bauza wrote: Le 17/11/2015 20:25, Sean Dague a écrit : On 11/17/2015 01:48 PM, Matt Riedemann wrote: On 11/17/2015 11:28 AM, Alexis Lee wrote: Often in Nova we introduce an option defaulted off (so as not to break people) but then we want to make it default

Re: [openstack-dev] [Fuel] HA cluster disk monitoring, failover and recovery

> On 18 Nov 2015, at 4:52 AM, Alex Schultz wrote: > > On Tue, Nov 17, 2015 at 11:12 AM, Vladimir Kuklin > wrote: >> Bogdan >> >> I think we should firstly check whether attribute deletion leads to node >> starting its services or not. From what I

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

On Tue, Nov 17, 2015 at 4:38 PM, Cody Herriges wrote: > Now that the standard is $::os_service_default does it mean that current > changes up for review with parameters set to the string ' DEFAULT>' should be changed to $::os_service_default before merge? > The decision was

Re: [openstack-dev] [stable] Making stable maintenance its own OpenStack project team

On 11/13/2015 8:10 AM, Thierry Carrez wrote: So.. quick summary of this thread so far. (-) * Not enough work to warrant a designated "team", now that the work is decentralized and the cats are mostly herding themselves * The change is unlikely to bring a meaningful improvement to the

Re: [openstack-dev] [Fuel] Number of IP addresses in a public network

Folks, we should resurrect this thread and find a consensus. > 1 вер. 2015 р. о 15:00 Andrey Danin написав(ла): > > +1 to Igor. > > It's definitely not a High bug. The biggest problem I see here is a confusing > error message with a wrong number of required IPs. AFAIU we

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

Iury Gregory wrote: > Hi Cody, > If there is patches using $::os_service_default and they are blocked, I > think the owner just need to request removal and continue the work.( I > think ) > Iury, Now that the standard is $::os_service_default does it mean that current changes up for review

[openstack-dev] [magnum] Autoscaling both clusters and containers

Hi all, I was having a discussion with a teammate with respect to container scaling. He likes the aspect of nova-docker that allows you to scale (essentially) infinitely almost instantly, assuming you are using a large pool of compute hosts. In the case of Magnum, if I'm a container user, I

Re: [openstack-dev] [openstack-infra] Adding new members to new vitrage-dashboard-core group in gerrit is disabled

Thank you! Regarding question 2 - I found the way. On 11/18/15, 00:22, "Elizabeth K. Joseph" wrote: >On Tue, Nov 17, 2015 at 5:17 AM, GROSZ, Maty (Maty) > wrote: >> Two questions regarding new project init: >> >> 1) A new change,

Re: [openstack-dev] [networking-ovs-dpdk]

Thanks a lot Sean, that was helpful. Changing the target from ivshmem to native-linuxapp removed the error and it doesn't hang at creating external bridge anymore. All processes(nova-api, neutron, ovs-vswitchd, etc) did start. Thanks, Prathyusha On Tue, Nov 17, 2015 at 7:57 PM, Mooney, Sean K

Re: [openstack-dev] [nova][infra] Getting a bleeding edge libvirt gate job running

On Tue, Nov 17, 2015 at 03:32:45PM -0800, Jay Pipes wrote: > On 11/17/2015 11:10 AM, Markus Zoeller wrote: > >Background > >== > >The blueprint [1] wants to utilize the *virtlogd* logging deamon from > >libvirt. Among others to solve bug [2], one of our oldest ones. The > >funny part is,

Re: [openstack-dev] [neutron][tap-as-a-service] weekly meeting

hi, On Thu, Nov 12, 2015 at 2:11 AM, Vikram Hosakote (vhosakot) wrote: > Hi, > > TAAS looks great for traffic monitoring. > > Some questions about TAAS. > > 1) Can TAAS be used for provider networks as well, or just for tenant > networks ? currently only for VM ports on

  1   2   >