Re: [openstack-dev] [mistral] How to call 3rd-party tools(such as Ansible) in Mistral

> On 19 Oct 2015, at 07:53, WANG, Ming Hao (Tony T) > wrote: > > The “custom action” needs to re-install Mistral. > If the Mistral service is part of 3rd party OpenStack, it may be unacceptable > to let every user create his own customer action. What do you think? Yes, correct. It requires re

[openstack-dev] [Neutron][Metering]How does metering agent work to calc traffic?

Hi, all In order to calc bandwidth, how does metering agent work? For example, how does iptables looks like if I have a floating ip? I find some instructions about metering agent in https://wiki.openstack.org/wiki/Neutron/Metering/Bandwidth. And there is iptables picture, but it is not clea

Re: [openstack-dev] [neutron][stable] proactive backporting

> On 16 Oct 2015, at 17:36, Salvatore Orlando wrote: > > This sounds like a pretty decent idea to me. Considering Neutron's patch > merge rate this activity should hopefully not take a consistent chunk of your > Friday. Actually, it does, if you consider other stable maintenance activities lik

Re: [openstack-dev] [neutron][stable] proactive backporting

> On 16 Oct 2015, at 23:04, Edgar Magana wrote: > > + 2 and total support for it. > > Looking forward to reviewing the first set of them. If we talk about actual backports on review, they are always there. I suggest folks that are interested in stable branches to use the Kyle’s dashboard: htt

Re: [openstack-dev] [mistral] How to call 3rd-party tools(such as Ansible) in Mistral

Renat, Thanks for your info. I like your option2(https://blueprints.launchpad.net/mistral/+spec/action-providers). ☺ Any schedule for this? Looks like it isn’t started yet. Thanks, Tony From: Renat Akhmerov [mailto:[email protected]] Sent: Monday, October 19, 2015 2:58 PM To: OpenStack Dev

Re: [openstack-dev] [neutron][stable] proactive backporting

> On 17 Oct 2015, at 00:26, Armando M. wrote: > > I am pretty confident that the experience you went through was an exception > rather than the rule. We're pretty flexible and allow a patch to go in > (master) with a promise of a follow up, if it's critical backport. The > important thing is t

Re: [openstack-dev] [neutron][stable] proactive backporting

> On 16 Oct 2015, at 19:09, Sean M. Collins wrote: > > On Fri, Oct 16, 2015 at 11:36:13AM EDT, Salvatore Orlando wrote: >> It might also make sense to ask contributors to resume the habit of tagging >> bugs with 'backport-potential' even if not in the RC period. > > I like this idea because it'l

[openstack-dev] Fwd: [nova][mistral] Automatic evacuation as a long running task

Accidentally sent this privately. -- Forwarded message -- From: Matthew Booth Date: Fri, Oct 9, 2015 at 6:14 PM Subject: Re: [openstack-dev] [nova][mistral] Automatic evacuation as a long running task To: "Deja, Dawid" On Thu, Oct 8, 2015 at 12:51 PM, Deja, Dawid wrote: > Hi

Re: [openstack-dev] [Neutron] [Tempest] where fwaas tempest tests should be?

> On 16 Oct 2015, at 10:50, Takashi Yamamoto wrote: > > if i move fwaas tests from neutron to neutron-fwaas, [1] > is there easy way to run them together with the rest of neutron api tests > for gate-neutron-dsvm-api job? Before we jump in to reflect current gating status-quo, do we have a defin

Re: [openstack-dev] [neutron] Neutron rolling upgrade - are we there yet?

Hello Artur, thanks for staring this thread. See inline please. On 10/15/2015 05:23 PM, Ihar Hrachyshka wrote: Hi Artur, thanks a lot for caring about upgrades! There are a lot of good points below. As you noted, surprisingly, we seem to have rolling upgrades working for RPC layer. Before we

Re: [openstack-dev] [oslo] Require documenting changes with versionadded and versionchanged

> On 16 Oct 2015, at 13:02, Victor Stinner wrote: > > Le 15/10/2015 17:54, Joshua Harlow a écrit : >> I had this problem with deprecation versioning (the debtcollector >> library functions take a version="XYZ", removal_version="ABC" params, >> see >> http://docs.openstack.org/developer/debtcollec

Re: [openstack-dev] [neutron] Neutron rolling upgrade - are we there yet?

Rossella Sblendido wrote: Hello Artur, thanks for staring this thread. See inline please. On 10/15/2015 05:23 PM, Ihar Hrachyshka wrote: Hi Artur, thanks a lot for caring about upgrades! There are a lot of good points below. As you noted, surprisingly, we seem to have rolling upgrades worki

[openstack-dev] [mistral] Cancelling team meeting today - 10/19/2015

Team, let’s cancel today’s meeting since we all have lots of pre-summit activities. Just in case if you still want to add your topics to discuss at the summit, here’s the link to the etherpad again: https://etherpad.openstack.org/p/mistral-tokyo-summit-2015

Re: [openstack-dev] Blueprint to change (expand) traditional Ethernet interface naming schema in Fuel

Hello, Continue work on the Ethernet interfaces naming schema I create the blueprint and spec for review: https://blueprints.launchpad.net/fuel/+spec/network-interfaces-naming-schema https://review.openstack.org/#/c/236848/ Because proposed changes potentially affect different components (and act

Re: [openstack-dev] [fuel] PTL & Component Leads elections

Hi folks, it's time to start voting for the component leads. There was only one candidate for the Fuel Python Component Lead, so, no need for voting. Congrats to Igor Kalnitsky! For the Fuel Library Component Lead we have two candidates and you should receive an email with title "Poll: Fuel Libr

Re: [openstack-dev] [neutron][stable] proactive backporting

> -Original Message- > From: Ihar Hrachyshka [mailto:[email protected]] > Sent: Friday, October 16, 2015 1:34 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: [openstack-dev] [neutron][stable] proactive backporting > > Hi all, > > I’d like to introduce a

Re: [openstack-dev] [Nova] Migration state machine proposal.

Hi, all, If you don't mind, how about approve the BP, and I can start this work. Thanks. On 10/15/2015 04:53 PM, Tang Chen wrote: Hi all, The spec is now available here: https://review.openstack.org/#/c/235169/ Please help to review. Thanks. On 10/14/2015 10:05 AM, Tang Chen wrote: Hi, a

Re: [openstack-dev] [neutron][stable] proactive backporting

I thought that may be, some of the work Ihar is proposing, could be automated. Like, for example, checking if bug fixes are backportable as-is to the previous stable branches, and if they pass testing. If that's the case, the bot could automatically automatically add the bug to the list, or

Re: [openstack-dev] [oslo] Require documenting changes with versionadded and versionchanged

Victor, I'd like to continue the fast paced oslo releases. Last fire drill showed, a few projects that depended on internals of how things we implemented in oslo libraries. Examples were oslo.policy switching to requests from urllib3 and the oslo.utils how it deals with exceptions for example. The

Re: [openstack-dev] [Neutron] [Tempest] where fwaas tempest tests should be?

hi, On Mon, Oct 19, 2015 at 2:52 PM, Takashi Yamamoto wrote: > hi, > > On Thu, Oct 15, 2015 at 11:22 PM, Matthew Treinish > wrote: >> On Thu, Oct 15, 2015 at 09:02:22AM -0400, Assaf Muller wrote: >>> On Thu, Oct 15, 2015 at 7:25 AM, Takashi Yamamoto >>> wrote: >>> >>> > hi, >>> > >>> > i'm loo

Re: [openstack-dev] [Neutron] [Tempest] where fwaas tempest tests should be?

hi, On Mon, Oct 19, 2015 at 5:33 PM, Ihar Hrachyshka wrote: >> On 16 Oct 2015, at 10:50, Takashi Yamamoto wrote: >> >> if i move fwaas tests from neutron to neutron-fwaas, [1] >> is there easy way to run them together with the rest of neutron api tests >> for gate-neutron-dsvm-api job? > > Befor

[openstack-dev] [Fuel][Plugins] Plugin deployment questions

Hi There, There are situations where we’d like to deploy only Fuel plugins in an environment. That’s typically the case with Elasticsearch and InfluxDB plugins of LMA tools. Currently it’s not possible because you need to at least have one controller. What exactly is making that limitation? How h

Re: [openstack-dev] [Nova] Migration state machine proposal.

On 10/19/2015 11:13 AM, Tang Chen wrote: > Hi, all, > > If you don't mind, how about approve the BP, and I can start this work. > This is IMHO the biggest drawback of the current spec process (as I've written before). There is no reason why you should doubt that this particular spec will get ap

Re: [openstack-dev] [mistral] How to call 3rd-party tools(such as Ansible) in Mistral

Dmitri, >From StackStorm's document, it can run Mistral's workflow, and Mistral >workflow can call StackStorm custom actions. Could you please help to explain how it is implemented? examples.mistral-basic: description: A basic workflow that runs an arbitrary linux command. type: direct

Re: [openstack-dev] [puppet][Fuel] Using Native Ruby Client for Openstack Providers

On 14/10/15 17:15, Gilles Dubreuil wrote: > > > On 14/10/15 10:36, Colleen Murphy wrote: >> >> >> On Tue, Oct 13, 2015 at 6:13 AM, Vladimir Kuklin > > wrote: >> >> Puppetmaster and Fuelers, >> >> Last week I mentioned that I would like to bring the theme of

Re: [openstack-dev] [puppet][Fuel] Using Native Ruby Client for Openstack Providers

On 13/10/15 21:13, Vladimir Kuklin wrote: Puppetmaster and Fuelers, Last week I mentioned that I would like to bring the theme of using native ruby OpenStack client and use it within the providers. Emilien told me that I had already been late and the decision was made that puppet-openstack deci

[openstack-dev] [cloudkitty] IRC meetings canceled for two weeks

Hi, The summit is coming and most people are already in Japan. This makes the organisation of meetings pretty difficult. We'll cancel this week's meeting and next weeks too as most of the contributors will be in Tokyo talking CloudKitty's future. We'll resume normal schedule after the summit. Ch

[openstack-dev] [nova] Next Nova meeting on November 4th 2015

Hi, Due to the summit, we decided the next meeting will be: November 4th 2015 2100 UTC, #openstack-meeting http://www.timeanddate.com/worldclock/fixedtime.html?iso=20151104T21 For more details, as usual, please see: https://wiki.openstack.org/wiki/Meetings/Nova As normal, any questions, plea

Re: [openstack-dev] [Glance] Mitaka spec freeze proposal

On 16/10/15 16:34 +0900, Flavio Percoco wrote: Hi Glancers, Among the things we'd like to give a try to during Mitaka, we also have having a spec freeze. This was discussed in the latest drivers meeting[0] and you can find some extra details below. The freeze will happen after M-1 is cut and be

Re: [openstack-dev] [Nova] Migration state machine proposal.

Hi Nikola, On 10/19/2015 06:52 PM, Nikola Đipanov wrote: On 10/19/2015 11:13 AM, Tang Chen wrote: Hi, all, If you don't mind, how about approve the BP, and I can start this work. This is IMHO the biggest drawback of the current spec process (as I've written before). There is no reason why y

[openstack-dev] [Fuel][Plugins][Ironic] Deploy Ironic with fuel ?

Hello, I'm currently searching for information about Ironic Fuel plugin : https://github.com/openstack/fuel-plugin-ironic I don't find any documentation on it. I've tried to install and deploy an Openstack environment with Fuel 7.0 and Ironic plugin but it failed. After adding ironic role to a

Re: [openstack-dev] [cinder] NFS mount as cinder user instead of root

On 10/14/15 6:31 AM, Francesc Pinyol Margalef wrote: > Hi, > Yes, that worked! Thanks! :) > > But the process is very slow (about half an hour to create a volume). > I think the problem is the execution of "du -sb --apparent-size > --exclude *snapshot* > /var/lib/cinder/mnt/9ae799cf301b19940950ae4

Re: [openstack-dev] [mistral] How to call 3rd-party tools(such as Ansible) in Mistral

Dmitri, I think I got it. "st2/st2common/st2common/util/workflow/mistral.py" StackStorm uses function "_transform_action" here to transform action from StackStorm action style to "st2.action" style, and then call Mistral to execute workflow, since "st2.action" is Mistral's custom action. Please

[openstack-dev] [nova] Nova API sub-team meeting

Hi, We have weekly Nova API meeting this week. The meeting is being held Tuesday UTC1200. In other timezones the meeting is at: EST 08:00 (Tue) Japan 21:00 (Tue) China 20:00 (Tue) United Kingdom 13:00 (Tue) The proposed agenda and meeting details are here: https://wiki.openstack.org/wiki/Meeti

Re: [openstack-dev] [Fuel][Plugins] Plugin deployment questions

Hello folks, I second Patrick's idea. In our case we would like to install standalone RabbitMQ cluster with Fuel reference architecture to perform destructive tests on it. Requirement to install controller is an excessive burden in that case. Thanks, Dmitry 2015-10-19 13:44 GMT+03:00 Patrick Pe

[openstack-dev] Cross-project meeting, Tue Oct 20th, 21:00 UTC

Dear PTLs, cross-project liaisons, and interested team members, We'll have a cross-project meeting tomorrow at 21:00 UTC, with the following agenda: https://wiki.openstack.org/wiki/Meetings/CrossProjectMeeting#Proposed_agenda Review past action items Team announcements (horizontal, verti

Re: [openstack-dev] [all] jobs that make break when we remove Devstack extras.d in 10 weeks

From now until the removal of devstack extras.d support I'm going to  send a weekly email of jobs that may break. A warning was added that we  can track in logstash.  Hey! Thanks for notification! Murano team is on track to drop support usage of extras.d. [0] [0] https://review.op

[openstack-dev] [puppet] weekly meeting #56

Hello! Here's an initial agenda for our weekly meeting, tomorrow at 1500 UTC in #openstack-meeting-4: https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20151020 Note: some people have some actions, please have a look at the etherpad! Feel free to add any items you'd like to discu

Re: [openstack-dev] [Cinder] New extension API for detecting cinder-backup ?

On Fri, 2015-10-16 at 17:36 +, Ramakrishna, Deepti wrote: > Thanks Duncan. > > Should I publish a BP and spec for this? And follow it up with code > changes to the server, client, horizon and documentation? > > Thanks, > Deepti > I believe a BP and spec is required as this is a new API

Re: [openstack-dev] [Ironic] Driver documentation in Ironic

On 10/19/2015 01:46 AM, Wan-yen Hsu wrote: I fully agreed with Ramesh. There is a need for driver owners to be able to quickly update their driver’s document. Particularly, vendor's drivers have strong dependencies on their platform’s firmware. For instance, a new release of firmware may hav

Re: [openstack-dev] [Ironic] Driver documentation in Ironic

Hi Ramesh, On 15 October 2015 at 11:53, Ramakrishnan G wrote: > > > So what all are the problems ? > 1) Ability to update the driver documentation not-related to Ironic easily > without waiting. > 2) To save some core reviewers time who might not be familiar with the > hardware. > > To solve the

Re: [openstack-dev] [all] jobs that make break when we remove Devstack extras.d in 10 weeks

On 10/19/2015 08:48 AM, Victor Ryzhenkin wrote: >> From now until the removal of devstack extras.d support I'm going to >> send a weekly email of jobs that may break. A warning was added >> that we >> can track in logstash. > > Hey! > > Thanks for notification! > Murano team is

Re: [openstack-dev] [Ironic] Driver documentation in Ironic

Hi Wan-yen, On 19 October 2015 at 01:46, Wan-yen Hsu wrote: > > > I fully agreed with Ramesh. There is a need for driver owners to be able > to quickly update their driver’s document. Particularly, vendor's drivers > have strong > What do you mean by 'quickly'? Quicker than it has been in th

[openstack-dev] [cross-project] Admin

While I tend to play up bug 968696 for dramatic effect, the reality is we have a logical contradiction on what we mean by 'admin' when talking about RBAC. In early iterations of OpenStack, roles were global. This is reflected in many of the Policy checks that only look for the global role.

Re: [openstack-dev] ERROR : openstack Forbidden (HTTP 403)

On 10/18/2015 02:25 AM, Emilien Macchi wrote: WARNING: keystoneclient.auth.identity.generic.base Discovering versions from the identity service failed when creating the password plugin. Attempting to determine version from URL. What is the AUTH_URL? This warning alone is not a problem, but it

Re: [openstack-dev] [Neutron] Design Summit Session - Containers Orchestration platforms Integration with Neutron

On Sun, Oct 18, 2015 at 1:54 PM, Murali R wrote: > Will there be an irc opened for these sessions to join remotely? > > We will have people in the room who will be on IRC, yes, just use #openstack-neutron. Even better, you can comment on the etherpad live while the session is going on, which is a

[openstack-dev] [ceilometer] ceilometer+ops session

hi folks, to followup on an item regarding Ceilometer+ops session at the summit. there isn't one explicitly for Ceilometer but there is a monitoring session[1] and a billing session[2]. based on the past, these sessions tend to focus more on 3rd party tools such as Sensu et al but if free it

[openstack-dev] [oslo][log][ossg] Log and OSSG working group session (Re: [oslo] Design Summit Schedule)

Folks, We've added: http://mitakadesignsummit.sched.org/event/33df7147d064a37bbffbc44c0ae45824 to discuss topics related to oslo.log/oslo.rootwrap/oslo.privsep etc. Please let me know if the schedule works. Thanks, Dims On Wed, Oct 14, 2015 at 11:04 AM, Davanum Srinivas wrote: > Folks, > > He

Re: [openstack-dev] [Neutron] Design Summit Session - Containers Orchestration platforms Integration with Neutron

On Oct 19, 2015 7:31 AM, "Kyle Mestery" wrote: > > On Sun, Oct 18, 2015 at 1:54 PM, Murali R wrote: >> >> Will there be an irc opened for these sessions to join remotely? >> > We will have people in the room who will be on IRC, yes, just use #openstack-neutron. Even better, you can comment on the

[openstack-dev] [cinder] Rolling upgrades - missing pieces

Hi all, One of our priority goals for Liberty was the adoption of oslo.versionedobjects in order for Cinder to achieve ability to do rolling upgrades. We weren't successful with that in L, and work got postponed to Mitaka. I want to highlight remaining work in that topic as well as other pieces th

Re: [openstack-dev] [Congress] Congress and Monasca Joint Session at Tokyo Design Summit

Fabio, I haven't heard back on this so I'm assuming Wed 3:40-4:20 works for you. Tim On Wed, Oct 14, 2015 at 10:51 AM Tim Hinrichs wrote: > Hi Fabio, > > We now have a schedule. I've tentatively booked you for half of our slot > Wed 3:40-4:20. Does that work for your team? You can find the

[openstack-dev] Volunteer for JetBrains License Management

Hi Devs, I will be starting a new job in a couple weeks, and as such will be leaving my current job and the OpenStack community by the end of this week. That means we will need a new representative to manage the Open Source licenses JetBrains has given us, and to manage that relationship. So,

Re: [openstack-dev] [fuel] OpenStack versioning in Fuel

Oleg, I think we can remove this function for new releases and keep them only for backward compatibility with previous ones. Why not? If there's a way to do things better let's do them better. :) On Sat, Oct 17, 2015 at 11:50 PM, Oleg Gelbukh wrote: > In short, because of this: > https://github.

Re: [openstack-dev] [Zaqar][cli][openstackclient] conflict in nova flavor and zaqar flavor

Thanks for the awesome feedback :) I got the point of not using project name, thanks Dean for explaining it so well. We will move ahead as per Monty's suggestion. On Wed, Oct 14, 2015 at 3:13 PM, Sean Dague wrote: > On 10/12/2015 07:55 PM, Dean Troyer wrote: > > On Mon, Oct 12, 2015 at 5:25 PM,

Re: [openstack-dev] [Fuel] Modularization activity POC

Hey Evgeniy. This is awesome news1 I believe that microservices is way to go. Despite the fact that them bring a set of classical problems (e.g. duplication of domain entities) we will win more than loose. :) If there will be any specs or design meetings, please send me invite - I'd gladly join d

Re: [openstack-dev] [cross-project] Admin

+1. I think there may be a slight issue with this and Heat, or any other service depending on Heat though. It would have to be very carefully through through, since Heat acts on behalf of the user as the User him/herself would, so scoping may need to interact differently there, then say Nova. M

Re: [openstack-dev] [cross-project] Admin

On 10/19/2015 11:53 AM, Fox, Kevin M wrote: +1. I think there may be a slight issue with this and Heat, or any other service depending on Heat though. It would have to be very carefully through through, since Heat acts on behalf of the user as the User him/herself would, so scoping may need t

Re: [openstack-dev] [cinder] Rolling upgrades - missing pieces

On Mon, Oct 19, 2015 at 03:10:16PM +, Dulko, Michal wrote: > Hi all, > > One of our priority goals for Liberty was the adoption of > oslo.versionedobjects in order for Cinder to achieve ability to do > rolling upgrades. We weren't successful with that in L, and work got > postponed to Mitaka.

[openstack-dev] [keystone] [nova] [cinder] Mitaka summit working session: Resource Federation for an Open Cloud

Hello everyone, Since the Liberty summit, we have been working on prototyping the changes needed for inter-Openstack deployment resource federation[1]. We now have a demo to show, in which users can attach Cinder volumes to Nova instances in other Openstack deployments. Although all of our change

Re: [openstack-dev] [Fuel] Assigning VIPs on network config serialization

Hi Roman, > Not assign addresses to VIPs is a network configuration is being > serialized for API output. AFAIK, that's not truth. Fuel UI and OSTF relies only on *public* VIP. So we can keep only *public* VIP, and do not assign / show others. > Check number of IP addresses wherever it is possib

[openstack-dev] [nova] Checking dates for the Mitaka Nova Midcycle

Hi, We have a few offers for midcycle dates. If you would like to attend, please let me know if: * the proposed date works for you * one of the proposed venues is a no go (budget or otherwise) http://doodle.com/poll/88sbzgcv28rww2n3 Thanks, johnthetubaguy PS If doodle doesn't work for you, let

Re: [openstack-dev] [cross-project] Admin

On 19/10/15 14:57, Adam Young wrote: > While I tend to play up bug 968696 for dramatic effect, the reality is > we have a logical contradiction on what we mean by 'admin' when talking > about RBAC. > > In early iterations of OpenStack, roles were global. This is reflected > in many of the Poli

Re: [openstack-dev] [app-catalog] [glance] [murano] Data Assets API for App Catalog

Alexander had been attending our meetings for a while, asking us to use Glance for the backend, and offering to provide a POC. We liked the idea and waited a while to see it. For example: http://eavesdrop.openstack.org/meetings/app_catalog/2015/app_catalog.2015-06-18-17.00.log.html http://eavesd

[openstack-dev] [nova] Nova's Mitaka Release Schedule

Hi, I have put together a list of proposed Nova specific deadlines: https://wiki.openstack.org/wiki/Nova/Mitaka_Release_Schedule We can go through what needs to change in that list during the summit, and in the nova IRC meeting following the summit. Thanks, johnthetubaguy PS Please note I have

Re: [openstack-dev] [cross-project] Admin

On 10/19/2015 12:39 PM, Neil Jerram wrote: On 19/10/15 14:57, Adam Young wrote: While I tend to play up bug 968696 for dramatic effect, the reality is we have a logical contradiction on what we mean by 'admin' when talking about RBAC. In early iterations of OpenStack, roles were global. This

Re: [openstack-dev] [neutron][networking-ovn][l3] Add/delete router interface

> On Oct 17, 2015, at 2:11 PM, Ben Pfaff wrote: > >> On Fri, Oct 16, 2015 at 07:05:44PM -0700, Chandra Sekhar Vejendla wrote: >> The reason for the failure of these tests has got to do with the way >> OVN handles router interface. In openstack multiple subnets can be >> added to a network and f

Re: [openstack-dev] [cross-project] Admin

Maybe I misunderstood then. I was thinking you were proposing endpoint scoped tokens. But heat calls out to other endpoints itself, so if a token is scoped to heat, it can't relay it further. Thanks, Kevin From: Adam Young [[email protected]] Sent: Monday, Octobe

[openstack-dev] [Fuel] Testing before switching to upstream librarian

Hi Fuelers, It seems we have a regression on two critical bugs because of switching Fuel to puppet-openstacklib: https://bugs.launchpad.net/fuel/+bug/1507685 This regressed to patches that were in Fuel Library that addressed two bugs marked as Critical. We should improve the acceptance criteria

Re: [openstack-dev] [cross-project] Admin

On 10/19/2015 12:50 PM, Fox, Kevin M wrote: Maybe I misunderstood then. I was thinking you were proposing endpoint scoped tokens. But heat calls out to other endpoints itself, so if a token is scoped to heat, it can't relay it further. Right...not proposing that. This is specifically for ope

Re: [openstack-dev] [Fuel] Assigning VIPs on network config serialization

Hi! I mostly agree with Igor, GET request should not produce changes (i.e. allocate VIPs). > VIP allocation should be performed when we run deployment. I want to give an explanation here. We have a ticket for 8.0 to give an ability to set arbitrary addresses for VIPs. So, at least some of VIPs c

Re: [openstack-dev] [cinder] RemoteFS drivers refactoring: move code, which works with images to separate classes

On 10/14/2015 12:09 AM, Sean McGinnis wrote: On Tue, Oct 13, 2015 at 07:01:45PM +, D'Angelo, Scott wrote: If you create a blueprint and a spec for this, the details can be discussed in the spec. Yes, something like this we should definitely have a spec and blueprint for. Please write up a

Re: [openstack-dev] [Fuel] Assigning VIPs on network config serialization

Aleksey, Thank you for input. > We have a ticket for 8.0 to give an ability to set arbitrary addresses for > VIPs That shouldn't affect proposed approach. The main idea is to return *allocated VIPs* but *do not allocate* them implicitly. > we also need to provide an ability to run CheckBeforeD

Re: [openstack-dev] [devstack] [neutron] A larger batch of questions about configuring DevStack to use Neutron

On 12/10/15 16:32, Sean M. Collins wrote: > On Thu, Oct 08, 2015 at 01:47:31PM EDT, Mike Spreitzer wrote: >> .. In the section http://docs.openstack.org/developer/devstack/guides/ >>> neutron.html#using-neutron-with-a-single-interface there is a helpful display of localrc contents.

[openstack-dev] [app-catalog] IRC Meeting Thursday November 5th at 17:00 UTC

Hello all! Due to the summit we will cancel the next two weeks of IRC meetings for the App Catalog. The next meeting will be Thursday November 5th at 17:00UTC on #openstack-meeting-3 The agenda can be found here: https://wiki.openstack.org/wiki/Meetings/app-catalog I expect we'll have a lot to

Re: [openstack-dev] [cinder] Rolling upgrades - missing pieces

On Mon, 2015-10-19 at 11:19 -0500, Sean McGinnis wrote: > On Mon, Oct 19, 2015 at 03:10:16PM +, Dulko, Michal wrote: > > Hi all, > > > > One of our priority goals for Liberty was the adoption of > > oslo.versionedobjects in order for Cinder to achieve ability to do > > rolling upgrades. We wer

[openstack-dev] [openstack-operators][Tacker] BoF on NFV Orchestration using Tacker

Operators, Devs: Tacker team is soliciting inputs towards building the next set of features in the area of NFV Orchestration. We have the following Birds-of-a-Feather session to get together on this subject, When: Tuesday Oct 27, 2015 Where: OpenStack Tokyo Summit Link: http://sched.co/4MZc Some

[openstack-dev] [ironic] [horizon] ironic panels

Hi all, I am currently in the process of writing an Ironic panel in Horizon upstream. It was originally intended for this panel to be written in Angular JS, however, as I understand, no horizon angular work will merge for several months, and 2-3 panels (of which ironic is not one) are being move

Re: [openstack-dev] [Fuel] Testing before switching to upstream librarian

Hi, The policy should be revert, IMHO. cherry-pick doesn't guarantee the consistency, so it will take more time... Also this way gives time to write tests to exclude the regression in future. -- Best regards, Sergii Golovatiuk, Skype #golserge IRC #holser On Mon, Oct 19, 2015 at 6:52 PM, Matthe

Re: [openstack-dev] [Ironic] Driver documentation in Ironic

On Thu, Oct 15, 2015 at 09:23:18PM +0530, Ramakrishnan G wrote: > Hi All, > > This mail is related to driver-specific documentation in Ironic. > > First a bit of context. I work on iLO drivers in Ironic. Our team would > like to document both Ironic driver related stuff (which is related to > Ir

Re: [openstack-dev] [ironic] [horizon] ironic panels

The app catalog ui is using Angular almost exclusively. See: https://github.com/openstack/app-catalog-ui The Horizon developers have been quite supportive of using Angular in Horizon plugins. I think its been more of an issue migrating Python Horizion views to Angular in Horizon itself, not th

[openstack-dev] [designate] Update on Meetings + Code Freeze post Summit

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi All, Just a reminder that at the last IRC meeting [0] we decided a few things 1 - We are skipping 2 weeks or IRC meetings 2 - Due to the "big rename" [1] we are implementing a code freeze from the 10th -> 13th of November. The core team shou

Re: [openstack-dev] [ironic] [horizon] ironic panels

On Mon, Oct 19, 2015 at 07:05:04PM +0100, Beth Elwell wrote: > > Hi all, > > I am currently in the process of writing an Ironic panel in Horizon > upstream. It was originally intended for this panel to be written in > Angular JS, however, as I understand, no horizon angular work will > merge for

Re: [openstack-dev] [Fuel] Testing before switching to upstream librarian

Hi, First of all, I want to mention (I don't blame anyone), that two patchsets in bug description ([0], [1]) were not merged into upstream puppet-openstacklib module (and commit messages don't contain links to upstream review). I see only one proposed patch [2] from Dmitry Ilyin, which was abandon

[openstack-dev] [Ceilometer] "Infinite" values for "sum" and "average" fields in statistics query

Hi I have observed "inf" values for "sum" and "average" fields in a ceilometer statistics query on one of my custom meter as shown below. I have also verified the samples query for this meter and there are 1544 samples (output shown below) with all of them having value as "150.0". So ideally th

Re: [openstack-dev] Volunteer for JetBrains License Management

Hey Devs, Thanks again to those who expressed interest in taking this over! I've found a Core who was willing to take this over, Swapnil Kulkarni. For JetBrains licenses going forward please contact him at '[email protected]'. Thanks! Andrew From: Andrew Mel

Re: [openstack-dev] [Fuel] Testing before switching to upstream librarian

Hi, I agree with Ivan. Getting rid of forks and moving to puppet-librarian is complicated work and such problems are nearly unavoidable. It's hard to cover all possible corner cases with regular tests. openstacklib module provides basic functionality for many OpenStack modules, so reverting it to

Re: [openstack-dev] [Fuel] Assigning VIPs on network config serialization

On Mon, Oct 19, 2015 at 9:29 AM Igor Kalnitsky wrote: > Hi Roman, > > > Not assign addresses to VIPs is a network configuration is being > > serialized for API output. > > AFAIK, that's not truth. Fuel UI and OSTF relies only on *public* VIP. > So we can keep only *public* VIP, and do not assign

Re: [openstack-dev] [keystone] [nova] [cinder] Mitaka summit working session: Resource Federation for an Open Cloud

On Mon, Oct 19, 2015 at 12:27:53PM -0400, George Silvis, III wrote: > Hello everyone, > > Since the Liberty summit, we have been working on prototyping the > changes needed for inter-Openstack deployment resource federation[1]. > We now have a demo to show, in which users can attach Cinder volumes

[openstack-dev] [ironic] Ironic design summit schedule

Hi Jim, Is it possible to switch Group management session to Thursday? I have a techtalk at 2:30pm on Wednesday and it makes it very tight for me and Shiv to attend the group management at 2:50 pm. Since Shiv and myself are the proposer for the group management session, we want to be able

Re: [openstack-dev] [ironic] Ironic design summit schedule

On Mon, Oct 19, 2015 at 02:33:57PM -0700, Wan-yen Hsu wrote: > Hi Jim, > > Is it possible to switch Group management session to Thursday? I > have a techtalk at 2:30pm on Wednesday and it makes it very tight for me > and Shiv to attend the group management at 2:50 pm. Since Shiv and myself

Re: [openstack-dev] [Fuel] Core Reviewers groups restructure

Now that OpenStack Infra team has completed the stackforge namespace retirement and merged our ACL update [0], the rest of core reviewers cleanup is done: - creating tags and branches is now restricted to fuel-release group [1] - fuel-specs-core is populated as per proposal quoted below [2] [0] h

[openstack-dev] [Neutron] Mitaka Design Summit schedule for Neutron

Hi folks, The schedule for the Neutron project is published in [1]. We are still going through/ironing out some details, but for the most part (especially the order of sessions) we should be all set. See you in Tokyo! Cheers, Armando [1] http://mitakadesignsummit.sched.org/overview/type/neutron

[openstack-dev] [Horizon] Mitaka schedule and etherpads

The schedule for Horizon is published [1] and the initial etherpads are linked [2]. Happy typing. Looking forward to seeing everyone next week. David [1] http://mitakadesignsummit.sched.org/overview/type/horizon [2] https://wiki.openstack.org/wiki/Design_Summit/Mitaka/Etherpads#Horizon

[openstack-dev] [ironic] [neutron] Enforce port/portgroup MAC uniqueness constraint

Hi, In reference to comments on a patchset[1], port/portgroup addresses should be unique. Please also see the irc log[1] which includes earlier discussion regarding rationale. Q: How can we enforce this uniqueness across tables? [1] https://review.openstack.org/#/c/206232/26/ironic/db/sqlalche

[openstack-dev] [ironic] weekly subteam status report

Hi, Following is the subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) (diff with Oct 12, no diff for inspector) - Open: 150 (+7). 3 new (+1), 41 in progress (+5), 2 critical (+2), 11 high (-1) and 11 incomplete

[openstack-dev] [stable] Need group membership change for manila-stable-maint

I would like the manila-core group added as an included group in manila-stable-maint. I'm not sure what the right procedure is so I'm asking here. -Ben Swartzlander __ OpenStack Development Mailing List (not for usage que

Re: [openstack-dev] [neutron][calico] networking-calico 1.0.0

Great work Calico! Count me in when you have project meetings, I'd like to keep up. Carl On Oct 16, 2015 6:21 AM, "Neil Jerram" wrote: > I'm happy to announce the first release of networking-calico. As it > says at http://docs.openstack.org/developer/networking-calico/: > > networking-calico

Re: [openstack-dev] [Fuel] Modularization activity POC

This is great start, Evgeny. I have a few questions: 1. When do you expect to have POC to show? 2. Do you plan to put new services into separate repos? 3. How do you plan to package those - will you create RPM package for each, as well as Docker container (as we have everything in cont

Re: [openstack-dev] [fuel] PTL & Component Leads elections

Congrats Igor! Sergey - thanks for help. On Mon, Oct 19, 2015 at 2:48 AM Sergey Lukjanov wrote: > Hi folks, > > it's time to start voting for the component leads. > > There was only one candidate for the Fuel Python Component Lead, so, no > need for voting. Congrats to Igor Kalnitsky! > > For t

[openstack-dev] [kolla] Mitaka Summit Schedule

Kollians, I have produced the Mitaka design sessions based upon our previous voting about a month ago into the following schedule. I would update sched.org, but it is returning an error 500 presently. Once it is active again, I'll make sure the detailed schedule is placed into sched.org. htt

  1   2   >