Re: [openstack-dev] [Openstack][Neutron][Monasca]

Rubab Syed wrote: Hi, I'm doing a university project in OpenStack. The aim is to monitor virtual routers per tenant with Monasca(which according to my knowledge hasn't been implemented yet). The initial features would include monitoring of in/out traffic per

Re: [openstack-dev] [Manila] HDFS CI broken

- Original Message - > From: "Ben Swartzlander" > To: "OpenStack Development Mailing List (not for usage questions)" > > Sent: Wednesday, February 10, 2016 9:00:06 PM > Subject: [openstack-dev] [Manila] HDFS CI broken > > The

Re: [openstack-dev] [all] [tc] "No Open Core" in 2016

On 02/08/2016 09:54 PM, Flavio Percoco wrote: > Would our votes change if Poppy had support for OpenCDN (imagine it's being > maintained) even if that solution is terrible? Let's say it was doing that, and spawning instances containing OpenCDN running on a multi-datacenter OpenStack deployment,

Re: [openstack-dev] [Nova][Cinder] Multi-attach, determining when to call os-brick's connector.disconnect_volume

Hi, As far as I can see volume attachments are handled on attachment level today as opposed to host level in Cinder. How the volume is exposed to a host technically is another question, but conceptually Cinder is the ultimate source of truth regarding how many attachments a volume has and what

Re: [openstack-dev] [fuel] Supporting multiple Openstack versions

Hi, > So what is open? The composition layer. We can have different composition layers for every release and it's already implemented in releases - separate puppet modules/manifests dir for every release. > Currently, we just abandon support for previous versions in the composition layer and

Re: [openstack-dev] [TaskFlow] TaskFlow persistence

Hi Joshua, Yes, sure will do that once I get some window out of my work. One last query(hopefully :) ) , can the factory method be an instance method of a class? I tried giving it as "FlowFactory().flow_factory", where FlowFactory is my class name. It failed with below error: ValueError: Flow

Re: [openstack-dev] [Fuel][QA] What is the preferred way to bootstrap a baremetal node with Fuel on product CI?

Thanks to all for answers! We will leave Fuel master node on a VM for our testing until some specific cases will require it on a baremetal. Ironic looks like a good tool for PXE provisioning and manage other baremetal slaves via IPMI, we will investigate how it could be used in our testing tools

Re: [openstack-dev] [infra] [trove] gate jobs failing with ovh apt mirrors

On 2016-02-11 07:00:01 + (+), Craig Vyvial wrote: > I started noticing more of the Trove gate jobs failing in the last 24 hours > and I think i've tracked it down to this mirror specifically. > http://mirror.bhs1.ovh.openstack.org/ubuntu/pool/main/p/ > It looks like its missing the

Re: [openstack-dev] [neutron] [ipam] Migration to pluggable IPAM

--- John Belamaric (240) 383-6963 > On Feb 11, 2016, at 5:37 AM, Ihar Hrachyshka wrote: > > What’s the user visible change in behaviour after the switch? If it’s only > internal implementation change, I don’t see why we want to leave the choice > to operators. > It is

Re: [openstack-dev] Multiple delete of network through CLI is not available as of now

Welcome! Please check out Neutron's developer docs, specifically how we handle new features or work, to get started. http://docs.openstack.org/developer/neutron/policies/blueprints.html Please also check out our onboarding docs.

Re: [openstack-dev] [neutron] [ipam] Migration to pluggable IPAM

On Thu, Feb 11, 2016 at 3:32 AM, Ihar Hrachyshka wrote: > Salvatore Orlando wrote: > >> The difference lies in the process in my opinion. >> If the switch is added into the migration path then we will tell operators >> when to switch. >> I was

[openstack-dev] Multiple delete of network through CLI is not available as of now

Hello, I am monika. new to the openstack community.Having working experience in Python. I was going through the the neutron use-cases I observed that we can delete multiple network at a time through the dashboard but the same is not possible through the command line. But in the ironic component

Re: [openstack-dev] [neutron] [ipam] Migration to pluggable IPAM

On Feb 11, 2016, at 12:04 PM, Armando M. > wrote: On 11 February 2016 at 07:01, John Belamaric > wrote: It is only internal implementation changes. That's not entirely true, is it? There

Re: [openstack-dev] [magnum][heat] Bug 1544227

On Thu, Feb 11, 2016 at 5:23 PM, Hongbin Lu wrote: > Rabi, > > As you observed, I have uploaded two testing patches [1][2] that depends on > your fix patch [3] and the reverted patch [4] respectively. An observation is > that the test "gate-functional-dsvm-magnum-mesos"

Re: [openstack-dev] [Fuel][Plugins] Multi release packages

r/YACL/YAQL/ On Thu, Feb 11, 2016 at 9:35 PM, Ilya Kutukov wrote: > My opinion that i've seen no example of multiple software of plugins > versions shipped in one package or other form of bundle. Its not a common > practice. > > Anyway we need to provide ability to

Re: [openstack-dev] [neutron] [ipam] Migration to pluggable IPAM

On Thu, Feb 11, 2016 at 3:20 AM, Salvatore Orlando wrote: > The difference lies in the process in my opinion. > If the switch is added into the migration path then we will tell operators > when to switch. > I was suggesting doing it manual because we just don't know if

Re: [openstack-dev] [neutron] [ipam] Migration to pluggable IPAM

On Thu, Feb 11, 2016 at 10:04 AM, Armando M. wrote: > On 11 February 2016 at 07:01, John Belamaric > wrote: >> It is only internal implementation changes. > > That's not entirely true, is it? There are config variables to change and it > opens up the

[openstack-dev] [nova] Update on scheduler and resource tracker progress

Hello all, Performance working group, please pay attention to Chapter 2 in the details section. tl;dr - At the Nova mid-cycle, we finalized decisions on a way forward in redesigning the way that resources are tracked in Nova. This work is a major undertaking and has implications for

[openstack-dev] [mitaka][hackathon] Mitaka Bug Smash Hackathon in Bay Area (March 7-9)

Hi stackers, If you are in Bay Area and you would to work together with your friends from community on fixing non trivial bugs together, you have a great chance. There is going to be special event "Mitaka bug smash". Here is the full information:

Re: [openstack-dev] [infra][keystone][kolla][bandit] linters jobs

Andreas, Totally understand the overload problem with no short-term workarounds. I think all engineering in OpenStack is over capacity a bit and folks are really burning the midnight oil to make sure Mitaka is the best release of OpenStack yet! Please feel free to drop by #kolla and ping the

[openstack-dev] [qa] deprecating Tempest stress framework

In order to keep Tempest healthy I feel like it's time to prune things that are outside of the core mission, especially when there are other options out there. The stress test framework in tempest is one of those. It builds on other things in Tempest, but isn't core to it. I'd propose that

Re: [openstack-dev] [all] RFC - service naming registry under API-WG

On Wed, 10 Feb 2016, Sean Dague wrote: If there are concerns with this approach let me know. Otherwise I'll propose the repo tomorrow and try to keep this ball rolling. +1. It's a good plan. Thanks for keeping the distillery cooking. -- Chris Dent (�s°□°)�s�喋擤ォ�

Re: [openstack-dev] [all] [tc] "No Open Core" in 2016

On 11/02/16 17:31 +0800, Thomas Goirand wrote: On 02/08/2016 09:54 PM, Flavio Percoco wrote: Would our votes change if Poppy had support for OpenCDN (imagine it's being maintained) even if that solution is terrible? Let's say it was doing that, and spawning instances containing OpenCDN

Re: [openstack-dev] [neutron] [ipam] Migration to pluggable IPAM

Salvatore Orlando wrote: The difference lies in the process in my opinion. If the switch is added into the migration path then we will tell operators when to switch. I was suggesting doing it manual because we just don't know if every operator is happy about doing

Re: [openstack-dev] [Nova][Cinder] Multi-attach, determining when to call os-brick's connector.disconnect_volume

On Thu, Feb 11, 2016 at 12:23 PM, Daniel P. Berrange wrote: > As above, we need to solve this more generally than just multi-attach, > even single-attach is flawed today. > Agreed. This is what I was getting at. Because we have at least 3 different types of attach being

[openstack-dev] [release][stable] yaql 1.0.3 release (liberty)

We are overjoyed to announce the release of: yaql 1.0.3: YAQL - Yet Another Query Language This release is part of the liberty stable release series. For more details, please see below. Changes in yaql 1.0.2..1.0.3 e52b00d Bug in Lambda smart-type was fixed

Re: [openstack-dev] [neutron][tempest] No metadata route in test_dualnet* family

Evgeny Antyshev wrote: On 02/11/2016 01:48 PM, Ihar Hrachyshka wrote: Evgeny Antyshev wrote: Hello! I need an advice from someone familiar with how Neutron configures Metadata routes for created subnets. Below, I presume you enabled

Re: [openstack-dev] [Fuel][Plugins] Multi release packages

Sorry for the typo "s/I can shade more light/I can shed more light/" On Thu, Feb 11, 2016 at 1:51 PM, Evgeniy L wrote: > Hi, > > As an author of this part of pluggable architecture I can shade more light > on why it was implemented this way and why it's valuable to continue >

Re: [openstack-dev] [neutron] [ipam] Migration to pluggable IPAM

The difference lies in the process in my opinion. If the switch is added into the migration path then we will tell operators when to switch. I was suggesting doing it manual because we just don't know if every operator is happy about doing the switch when upgrading to Newton, but perhaps it is

Re: [openstack-dev] [qa] deprecating Tempest stress framework

+1 to that, it was my 2nd to-be-deprecated after javelin ;) El 11/02/16 a las 12:47, Sean Dague escribió: > In order to keep Tempest healthy I feel like it's time to prune things > that are outside of the core mission, especially when there are other > options out there. > > The stress test

Re: [openstack-dev] [Fuel] URL of Horizon is hard to find on the dashboard

Vitaly, What about adding some button with "Go" or "Visit" text? Somewhere on the right size of line? It'd be easy to understand what to click to visit the dashboard. - Igor On Thu, Feb 11, 2016 at 1:38 PM, Vitaly Kramskikh wrote: > Roman, > > For with enabled SSL it

[openstack-dev] Glance Image signing and verification

Hi, I am new in OpenStack and I want to create image through glance CLI and I am referring blueprint https://blueprints.launchpad.net/glance/+spec/image-signing-and-verification-support and I am using below mentioned command to create the image. So what is the step for Glance Image signing

Re: [openstack-dev] Glance Image signing and verification

Hi Pankaj, Here's a example instruction set for that feature. https://etherpad.openstack.org/p/liberty-glance-image-signing-instructions Hope it helps. On 2/11/16 8:45 AM, Pankaj Mishra wrote: > > Hi, > > > > I am new in OpenStack and I want to create image through glance CLI > and I am

[openstack-dev] [ironic] More midcycle details

Hi all, Our midcycle is next week! Here's everything you need to know. First and foremost, please RSVP on the etherpad, and add any topics (with your name!) that you'd like to discuss. https://etherpad.openstack.org/p/ironic-mitaka-midcycle Secondly, here are the time slots we'll be meeting at.

Re: [openstack-dev] [OpenStack-Infra] Gerrit downtime on Friday 2016-02-12 at 22:00 UTC

Hello! I have created a small patch [0] which is about renaming "openstack/fuel-plugin-astra” to "openstack/fuel-plugin-astara” (one character missing). Please also include it within Gerrit downtime. Thanks in advance. [0] https://review.openstack.org/#/c/279138/

Re: [openstack-dev] [infra] [trove] gate jobs failing with ovh apt mirrors

Jeremy, Thanks for looking at this. That makes sense but I'm not sure how to resolve this issue with the current diskimage-builder elements. If anyone has ideas it would be greatly appreciated. Thanks, -Craig Vyvial On Thu, Feb 11, 2016 at 8:44 AM Jeremy Stanley wrote: > On

[openstack-dev] [neutron] Broken Gate tests on branch stable/kilo, Project: openstack/neutron

I was trying to cherry pick a change in Liberty back to stable Kilo: https://review.openstack.org/#/c/277962/ Many of the gate tests failed and I notice that appears to be the case with most of the reviews going back a while in the past.From a quick check I did not see anything related to

Re: [openstack-dev] [Fuel][Plugins] Multi release packages

Hi, On Thu, Feb 11, 2016 at 11:46 AM, Igor Kalnitsky wrote: > Hey folks, > > The original idea is to provide a way to build plugin that are > compatible with few releases. It makes sense to me, cause it looks > awful if you need to maintain different branches for

Re: [openstack-dev] All hail the new per-region pypi, wheel and apt mirrors

On Wed, Feb 10, 2016 at 06:45:25PM -0600, Monty Taylor wrote: > Hey everybody, > > tl;dr - We have new AFS-based consistent per-region mirrors of PyPI and APT > repos with additional wheel repos containing pre-built wheels for all the > modules in global-requirements > > We've just rolled out a

Re: [openstack-dev] [magnum][heat] Bug 1544227

Rabi, As you observed, I have uploaded two testing patches [1][2] that depends on your fix patch [3] and the reverted patch [4] respectively. An observation is that the test "gate-functional-dsvm-magnum-mesos" failed in [1], but passed in [2]. That implies the reverted patch does resolve an

[openstack-dev] [QA][grenade] Create new grenade job

Hey QA. I am interested in making a Grenade job for Barbican and I have been messing around with Grenade. I downloaded the repo and ran the "grenade.sh" script but it seems it can't make it pastthe tempest smoke tests against the base. It fails on two tests. Is grenade suppose to work right

[openstack-dev] What's Up Doc? 12 Feb 2016

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi everyone, This week has been all about the Install Guide. We're locating pre-release packages now so we can begin testing in about two weeks' time. Please consider being a tester for this release. Even if you've never done it before, it's a

[openstack-dev] [nova] Updating a volume attachment

Hi, Currently there is no way to update the volume-attachment bdm parameters, i.e. the bus type or device name, without detaching and re-attaching the volume, and supplying the new parameters. This is obviously not ideal, and if the volume we want to update is the boot volume, detaching to update

Re: [openstack-dev] [neutron] [ipam] Migration to pluggable IPAM

On 10 February 2016 at 15:19, Carl Baldwin wrote: > On Thu, Feb 4, 2016 at 8:12 PM, Armando M. wrote: > > Technically we can make this as sophisticated and seamless as we want, > but > > this is a one-off, once it's done the pain goes away, and we won't be

Re: [openstack-dev] [neutron] [ipam] Migration to pluggable IPAM

On 11 February 2016 at 07:01, John Belamaric wrote: > > > --- > John Belamaric > (240) 383-6963 > > > On Feb 11, 2016, at 5:37 AM, Ihar Hrachyshka > wrote: > > > > What’s the user visible change in behaviour after the switch? If it’s > only internal

Re: [openstack-dev] [nova] Updating a volume attachment

Hi On 11/02/16 16:51, Shoham Peller wrote: > if the volume we want to update is the boot > volume, detaching to update the bdm, is not even possible. You might be interested in the approved spec [1] we have for Mitaka (ref. detach boot volume). Unfortunately the spec was not part of the

Re: [openstack-dev] [infra] [trove] gate jobs failing with ovh apt mirrors

Excerpts from Craig Vyvial's message of 2016-02-11 07:43:40 -0800: > Jeremy, > > Thanks for looking at this. That makes sense but I'm not sure how to > resolve this issue with the current diskimage-builder elements. If anyone > has ideas it would be greatly appreciated. > Any job using these

Re: [openstack-dev] [fuel] Supporting multiple Openstack versions

Hi, The Octane team has some issues with lacking definition of what the 'release' is in Fuel (in terms of managed environments). I started an etherpad [1] to summarize the entities/artifacts that consistute a 'release' at the moment. Based on this definition, we can localize and define entry

Re: [openstack-dev] [Manila] ALLOWED_EXTRA_MISSING is cover.sh

On Wed, Feb 10, 2016 at 6:39 PM, Valeriy Ponomaryov wrote: > Hello, John > > Note, that digit "4" defines amount of "python code blocks", not "python > code lines". So, you can have uncovered some log message that consists of > 100 lines. But it will be counted as just

Re: [openstack-dev] [neutron][tempest] No metadata route in test_dualnet* family

Evgeny Antyshev wrote: Hello! I need an advice from someone familiar with how Neutron configures Metadata routes for created subnets. Below, I presume you enabled isolated metadata in DHCP agent. We run tempest in such an environment that all ssh keys,

Re: [openstack-dev] [Fuel] URL of Horizon is hard to find on the dashboard

Roman, For with enabled SSL it still can be quite long as it contains FQDN. And we also need to change plugin link representation accordingly, which I don't fine acceptable. I think you just got used to the old interface where the link to Horizon was a part of deployment task result message.

Re: [openstack-dev] [nova] Updating a volume attachment

Thank you Andrea for your reply. I know this spec and it is indeed a viable solution. However, I think allowing users to update the attachment detail, rather than detach and re-attach a volume for every change is more robust and more convenient. Also, IMHO it's a better user-experience if users

Re: [openstack-dev] [Fuel][Plugins] Multi release packages

My opinion that i've seen no example of multiple software of plugins versions shipped in one package or other form of bundle. Its not a common practice. Anyway we need to provide ability to override paths in manifest (metadata.yaml). So the plugin developers could use this approaches to provide