Re: [openstack-dev] [TripleO] TripleO deep dive hour?

+1 great, looking forward to it. On Wed, Jun 29, 2016 at 5:29 AM, Victoria Martínez de la Cruz < victo...@vmartinezdelacruz.com> wrote: > +1 Awesome idea! > > 2016-06-28 20:01 GMT-03:00 Emilien Macchi : > >> Excellent idea, it would also be a good opportunity to take notes

Re: [openstack-dev] [mistal] Mistral logo ideas?

They all look good to me, and yes, I’d prefer mistral-tornado.png over mistral.png. I also have the same concern about Michal’s idea if it will be a small picture. Word “Mistral” may not be distinguishable. One more thing I’d like to add to the discussion: what if move away from having word

Re: [openstack-dev] [tricircle] About registering and loading a plugin

Hi all, I have succeed in registering a config option and obtaining it. So how to load an option from a customized file? Through cfg.CONF(default_config_files=[setup.cfg]? Still fails loading the config options in setup.cfg. Best regards, Yipei On Wed, Jun 29, 2016 at 8:36 AM, joehuang

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

Hi, team, After some feature spec patches merged and Mitaka tagging finished, and the feauture development is ongoing, the agenda of this weekly meeting is: IRC meeting: https://webchat.freenode.net/?channels=openstack-meeting on every Wednesday starting from UTC 13:00. # progress of

Re: [openstack-dev] [TripleO] TripleO deep dive hour?

On Tue, Jun 28, 2016 at 06:00:11PM -0400, James Slagle wrote: > We've got some new contributors around TripleO recently, and I'd like > to offer up a "TripleO deep dive hour". > > The idea is to spend 1 hour a week in a high bandwidth environment > (Google Hangouts / Bluejeans / ???) to deep dive

Re: [openstack-dev] [ironic] why do we need setting network driver per node?

My use case is supporting mixed hardware environments with hardware that has greater network capabilities and hardware without these capabilities without limiting my all my equipment to the lowest common feature set. The use case I’m describing will have some nodes configured with the neutron

Re: [openstack-dev] [craton] Developer weekly meeting scheduled every Thursday at 2100 UTC

On Wed, Jun 29, 2016 at 2:59 PM, Ian Cordasco wrote: > -Original Message- > From: Jim Baker > Reply: OpenStack Development Mailing List (not for usage questions) > > Date: June 29, 2016 at 14:08:25 > To:

[openstack-dev] [app-catalog] App Catalog IRC meeting Thursday June 30th

Join us Thursday for our weekly meeting, scheduled for June 30th at 17:00UTC in #openstack-meeting-3 The agenda can be found here, and please add to if you want to discuss something with the Community App Catalog team: https://wiki.openstack.org/wiki/Meetings/app-catalog Tomorrow we expect to

Re: [openstack-dev] [mistal] Mistral logo ideas?

+1 to the mistral-tornado.png logo, looks amazing! Thanks! Regards! --- Lingxian Kong On Tue, Jun 28, 2016 at 5:38 PM, Jason Rist wrote: > On 06/27/2016 06:57 AM, Dougal Matthews wrote: >> On 27 June 2016 at 07:45, Renat Akhmerov

Re: [openstack-dev] [Nova][Neutron][Live-Migration] Cross l2 agent migration and solving Nova-Neutron live migration bugs

On Tue, Jun 28, 2016 at 9:42 AM, Andreas Scheuring wrote: > I'm currently working on solving Nova-Neutron issues during Live > Migration. This mail is intended to raise awareness cross project and > get things kicked off. Thanks for sending this. > The issues >

Re: [openstack-dev] [security] [horizon] Security implications of exposing a keystone token to a JS client

Ah. I was going to bring this up eventually but hadn't gotten to it yet. I started up a patch for adding similar support for horizon here: https://review.openstack.org/#/c/311189/ My intention is to use it to make a Horizon Plugin to speak to a Keystone authenticated Kubernetes api directly.

Re: [openstack-dev] [kolla][keystone] is there chance the keystone cached the catalog and can not get the latest endpoints?

On Wednesday 29 June 2016 15:53:15 Kairat Kushaev wrote: > Hi, > Looks like this bug is duplicate of > https://bugs.launchpad.net/oslo.cache/+bug/1590779 Looks like it. > HTH > > Best regards, > Kairat Kushaev > > On Wed, Jun 29, 2016 at 3:32 PM, Jeffrey Zhang > >

Re: [openstack-dev] [tripleo] glance backend: replace swift by file in CI

On 06/28/2016 01:37 PM, Erno Kuvaja wrote: TL;DR Makes absolutely sense to run file backend on single node undercloud at CI. Few more comments inline. On Mon, Jun 27, 2016 at 8:49 PM, Emilien Macchi wrote: On Mon, Jun 27, 2016 at 3:46 PM, Clay Gerrard

Re: [openstack-dev] [Fuel] Deprecate fuel-upgrade repository

Hi Vladimir, This change is reasonable because the fuel-upgrade repository is not supported since the 8.0 release due to the fact that upgrade activities were consolidated in the fuel-octane repository. Also, as I know upgrade tarballs are no longer supported for the old releases (less or equal

Re: [openstack-dev] [kolla] Build the docker images in a graceful way

Hey Jeff, Can you write up a spec with the details? That way the community can see the full layout of the proposal. Thanks, -Ryan - Original Message - From: "Jeffrey Zhang" To: "OpenStack Development Mailing List" Sent:

Re: [openstack-dev] [kolla][keystone] is there chance the keystone cached the catalog and can not get the latest endpoints?

Yes it is the Bug. Thanks Kairat. On Wed, Jun 29, 2016 at 8:53 PM, Kairat Kushaev wrote: > Hi, > Looks like this bug is duplicate of > https://bugs.launchpad.net/oslo.cache/+bug/1590779 > HTH > > Best regards, > Kairat Kushaev > > On Wed, Jun 29, 2016 at 3:32 PM, Jeffrey

Re: [openstack-dev] [kolla] Build the docker images in a graceful way

Hi Jeffrey, Although I saw the Ansible Container repo, I wasn't that excited about it at the moment. It still feels complicated when compared to how Chef describes a container. However, it is still promising. On the reasons I did not choose to use it either is that Automated builds only handle

Re: [openstack-dev] [kolla] [tools] OpenStack client in a Docker container

Hi Jeffrey, On Wed, Jun 29, 2016 at 9:51 AM, Jeffrey Zhang wrote: > i am Interested in you Ansible scripts. Could u share it? Everything is on GitHub [1] (and Gitlab [2]). I have a constraint that I have to work with, and that is the Automated builds at the Docker

Re: [openstack-dev] [kolla] Build the docker images in a graceful way

On Wed, Jun 29, 2016 at 9:26 PM, Gerard Braad wrote: > "did Kolla drop support for > Fedora" ? > ​no one maintain the fedora and no gate for fedora too. So i am not sure whether the fedora works.​ -- Regards, Jeffrey Zhang Blog: http://xcodest.me

Re: [openstack-dev] [kolla] Build the docker images in a graceful way

On Wed, Jun 29, 2016 at 9:26 PM, Gerard Braad wrote: > Although I saw the Ansible Container repo, I wasn't that excited about > it at the moment. It still feels complicated when compared to how Chef > describes a container. However, it is still promising. > ​The ansible

Re: [openstack-dev] [kolla] [tools] OpenStack client in a Docker container

Gerard, The best way would be to make a jinja2 file out of your dockerfile and introduce it as an added container. Should be fairly straightforward but may require rework. Regards -steve On 6/28/16, 6:20 PM, "Gerard Braad" wrote: >Hi Steve, > > >How would you prefer me to

Re: [openstack-dev] [kolla] version of python2-oslo-config

Haikel, We are running master branch of rdo in master of kolla. Thanks Regards, -steve On 6/29/16, 3:45 AM, "Haïkel" wrote: >2016-06-28 17:53 GMT+02:00 Steven Dake (stdake) : >> The mitaka branch of Kolla requires 3.7 or later. >> >> Git checkout

[openstack-dev] [tripleo] Network diagram blueprint

Hello folks, Here is a blueprint that describes a new feature for the tripleo GUI: the network diagram. https://blueprints.launchpad.net/tripleo-ui/+spec/network-diagram I invite you to voice your opinions and share feedback. Thanks Honza Pokorny

Re: [openstack-dev] [tripleo] glance backend: replace swift by file in CI

On Wed, Jun 29, 2016 at 02:59:45PM +0200, Dmitry Tantsur wrote: > On 06/28/2016 01:37 PM, Erno Kuvaja wrote: > > TL;DR > > > > Makes absolutely sense to run file backend on single node undercloud at CI. > > > > Few more comments inline. > > > > On Mon, Jun 27, 2016 at 8:49 PM, Emilien Macchi

[openstack-dev] [lbaas][octavia] suggestion for today's meeting agenda: How to make the Amphora-agent support additional Linux flavors

Hello, Lately, I've been working on a fix[1] for the amhpora-agent, which currently only support Debian based flavors such as Ubuntu. The main Issues here: 1. NIC hot plugs: Ubuntu's ethX.cfg files looks different from ifcfg-ethX files which are accepted in Linux flavors such a RHEL, CentOS and

Re: [openstack-dev] Change in openstack/trove[master]: Ophaned Volume Not Removed on Instance Delete

Thanks for the pointers. These look good, and I'll keep an eye on them. :) Kevin From: Peter Stachowski [pe...@tesora.com] Sent: Wednesday, June 29, 2016 5:06 AM To: OpenStack Development Mailing List (not for usage questions); Ali Adil Subject: Re:

Re: [openstack-dev] [Fuel] Deprecate fuel-upgrade repository

This is yet another related patch [1], that removes the code from master branch and adds retirement warning. Review is welcome. [1] https://review.openstack.org/#/c/334949/ Vladimir Kozhukalov On Wed, Jun 29, 2016 at 4:00 PM, Ilya Kharin wrote: > Hi Vladimir, > > This

Re: [openstack-dev] [Cinder] Nominating Scott D'Angelo to Cinder core

One more vote from "not a core member" . I am not a core and I am mainly involved in the Nova project where Scott presence is always useful and valuable when we need to sort out some cinder <-> nova issue. -- Andrea Rosa On 27/06, Sean McGinnis wrote: > I would like to nominate Scott

Re: [openstack-dev] [tripleo] Network diagram blueprint

On 06/29/2016 08:50 AM, Honza Pokorny wrote: > Hello folks, > > Here is a blueprint that describes a new feature for the tripleo GUI: > the network diagram. > > https://blueprints.launchpad.net/tripleo-ui/+spec/network-diagram > > I invite you to voice your opinions and share feedback. > > Thanks

Re: [openstack-dev] [lbaas][octavia] suggestion for today's meeting agenda: How to make the Amphora-agent support additional Linux flavors

Interesting discussion, but the first question I’d ask is ‘why’ ? Unlike openstack server software, the amphora are meant to be black box appliance images, so why do we want to run different distros on them? Is there a deployment scenario you’re concerned with, or other use case? Thanks, doug

Re: [openstack-dev] [Cinder] Nominating Scott D'Angelo to Cinder core

Well, I do not belong to core group, but would like to vote for "*man with micro versions*" tattoo. Scott well deserves entry to this elite group.. he has always been there in nova-cinder interactions/discussions, micro versions and many other valuable additions to cinder component. Good luck

[openstack-dev] [octavia][upgrades] upgrade loadbalancer to new amphora image

Hi all, I was looking lately at upgrades for octavia images. This includes using new images for new loadbalancers, as well as for existing balancers. For the first problem, the amp_image_tag option that I added in Mitaka seems to do the job: all new balancers are created with the latest image

[openstack-dev] [Nova] No cells meeting today

Sorry for the late notice but based on an informal poll of the usual attendees due to the impending feature freeze everyone is busy with other things, and there wouldn't be much of anything to discuss this week. We will resume next week at the normal time.

Re: [openstack-dev] [lbaas][octavia] suggestion for today's meeting agenda: How to make the Amphora-agent support additional Linux flavors

Unfortunately I will be available on today meeting by phone so I’m not be able to discuss in way I would like to so I’m writing here. May you describe what you understand by that info about configuring agent binary on start? If I’m right the ideal situation would be like this: 1. We’re booting

Re: [openstack-dev] [lbaas][octavia] suggestion for today's meeting agenda: How to make the Amphora-agent support additional Linux flavors

> On 29 Jun 2016, at 18:10, Doug Wiegley wrote: > > Interesting discussion, but the first question I’d ask is ‘why’ ? > > Unlike openstack server software, the amphora are meant to be black box > appliance images, so why do we want to run different distros on

Re: [openstack-dev] [octavia][upgrades] upgrade loadbalancer to new amphora image

May you specify what exact use-case you have to upload incompatible images? In my opinion we should prepare a flow which is like you said building new instance, configuring everything, adding that amphora into load balancer and removing old one. In that way we will be able to minimize retry to

Re: [openstack-dev] [lbaas][octavia] suggestion for today's meeting agenda: How to make the Amphora-agent support additional Linux flavors

> On Jun 29, 2016, at 10:25 AM, Ihar Hrachyshka wrote: > > >> On 29 Jun 2016, at 18:10, Doug Wiegley wrote: >> >> Interesting discussion, but the first question I’d ask is ‘why’ ? >> >> Unlike openstack server software, the amphora are

Re: [openstack-dev] [lbaas][octavia] suggestion for today's meeting agenda: How to make the Amphora-agent support additional Linux flavors

I think we always expected other distros to be allowed, we just went with ubuntu/debian in the beginning bc most of us were comfortable with it. It would be nice to also get an image working with a micro version of "Company X" distro, if thats available. I'd gladly accept taht as the default

Re: [openstack-dev] [TripleO] TripleO deep dive hour?

On 06/28/2016 04:00 PM, James Slagle wrote: > We've got some new contributors around TripleO recently, and I'd like > to offer up a "TripleO deep dive hour". > > The idea is to spend 1 hour a week in a high bandwidth environment > (Google Hangouts / Bluejeans / ???) to deep dive on a TripleO

[openstack-dev] [swift] Support for unicode filename in tempurl middleware

Hi, I hope this is the right mailing list to ask this question. In case it's not, please direct me to the right one and apologise. I have some files stored in a container the use german character (and in general non ascii character). Using the swift REST APIs and python-swiftclient (3.0.0)

Re: [openstack-dev] [mistal] Mistral logo ideas?

On 06/29/2016 12:45 AM, Renat Akhmerov wrote: > They all look good to me, and yes, I’d prefer mistral-tornado.png over > mistral.png. I also have the same concern about Michal’s idea if it will be a > small picture. Word “Mistral” may not be distinguishable. > > One more thing I’d like to add to

Re: [openstack-dev] [TripleO] TripleO deep dive hour?

+1 , That would be really helpful .. On Wed, Jun 29, 2016 at 2:21 PM, Sanjay Upadhyay wrote: > +1 great, looking forward to it. > > On Wed, Jun 29, 2016 at 5:29 AM, Victoria Martínez de la Cruz < > victo...@vmartinezdelacruz.com> wrote: > >> +1 Awesome idea! >> >>

Re: [openstack-dev] [Fuel] Replace OSTF with Rally

Boris, can You take a look on HA scenarios [0] to give a quick feedback on how it should be implemented with Rally in right way? Plugins/templates/how yaml should look like. To make correct comparison of ostf and rally-based version. Thanks! [0] http://paste.openstack.org/show/523983/ On Tue,

Re: [openstack-dev] [TripleO] TripleO deep dive hour?

On Wed, Jun 29, 2016 at 3:30 AM, James Slagle wrote: > We've got some new contributors around TripleO recently, and I'd like > to offer up a "TripleO deep dive hour". > > The idea is to spend 1 hour a week in a high bandwidth environment > (Google Hangouts / Bluejeans /

Re: [openstack-dev] [TripleO] TripleO deep dive hour?

On Wed, Jun 29, 2016 at 4:57 PM, Swapnil Kulkarni (coolsvap) wrote: > On Wed, Jun 29, 2016 at 3:30 AM, James Slagle wrote: >> We've got some new contributors around TripleO recently, and I'd like >> to offer up a "TripleO deep dive hour". >> >> The idea

Re: [openstack-dev] [Nova] Questions about instance actions' update and finish

On Tue, Jun 28, 2016, at 09:27 PM, Zhenyu Zheng wrote: > How about I sync updated_at and created_at in my patch, and leave the > finish to the other BP, by this way, I can use updated_at for the > timestamp filter I added and it don't need to change again once the > finish BP is complete.

[openstack-dev] [trove] Trove meeting today (June 29th) is canceled

I'm canceling today's Trove meeting as there is nothing on the agenda and several people are either traveling or otherwise unable to make it to the meeting. We will meet again on July 6th. -amrith __ OpenStack Development

Re: [openstack-dev] [tricircle] About registering and loading a plugin

It may be better to attach setup.cfg you using, and paste traceback (if there). Cheers, Shinobu On Wed, Jun 29, 2016 at 4:57 PM, Yipei Niu wrote: > Hi all, > > I have succeed in registering a config option and obtaining it. So how to > load an option from a customized file?

[openstack-dev] [Fuel][Plugins] Transition of SDK to docs.openstack.org

Hi to everyone, please be informed that Fuel Plugin SDK is being migrated to docs.openstack.org to deliver a better dev. experience and versioning. the current version placed here [1] features the very initial revision of the SDK, with no specifics of the wiki page content [2]. *REQUEST:* if

[openstack-dev] [Fuel][Plugins] Fuel Plugin Builder 4.1.0 released!

Hey Fuelers, I'm glad to announce that FPB (fuel plugin builder) v4.1.0 has been released on PyPI [1]. It's mostly a maintenance release without new features. Here's a changelog highlights: * `tasks.yaml` is now optional for package version "4.0.0" [2] * Fuel Mitaka (9.0) is supported by

Re: [openstack-dev] [horizon] npm lint and test problems in gate

JFYI, CR [1] which fixes the corresponding bug [2] was merged on Jun 28, so it may make sense to recheck you perfectly looking commit if it has been staying in Gerrit for a while. [1] https://review.openstack.org/#/c/334582/ [2] https://bugs.launchpad.net/horizon/+bug/1595938 On Mon, Jun 27,

Re: [openstack-dev] [ironic] UFCG OneView CI comments missing recheck command

On 2016-06-29 00:23:36 + (+), Villalovos, John L wrote: [...] > Hopefully there is some standard for 3rd Party CI to use. [...] We've (Infra team) so far resisted the pressure to define a standardized grammar for triggering jobs through review comments since the goal is to eventually get

Re: [openstack-dev] [swift] Support for unicode filename in tempurl middleware

Hi Antonio, That sounds like a bug! Looks like we decode the temporal key coming in from the terminal, but don't properly encode it when getting the HMAC. This generates the UnicodeEncodeError on python 2.7, and I've submitted https://review.openstack.org/#/c/335615/ to address this. I'm not

Re: [openstack-dev] [tempest][nova][defcore] Add option to disable some strict response checking for interop testing

Chris, If we add openstack config to refstack submission will that provide sufficient info for "interoperability" LOGO? That includes version of APIs for each service. https://review.openstack.org/#/c/300057/ Thanks, Arkady -Original Message- From: Chris Hoge

Re: [openstack-dev] [Neutron][networking-sfc] NO networking-sfc project IRC meetings on 6/23/2016 and 6/30/2016

FYI. No networking-sfc project meeting this week due to some project members being either in Summit/Conference or on vacation,. We will resume our meeting next Thursday 7/7/2016. I have updated the meeting page for discussion topics. Feel free to add more if you have any. Thanks, Cathy From:

Re: [openstack-dev] [lbaas][octavia] suggestion for today's meeting agenda: How to make the Amphora-agent support additional Linux flavors

On Wed, Jun 29, 2016, at 10:26 AM, Nir Magnezi wrote: > Hello, > > Lately, I've been working on a fix[1] for the amhpora-agent, which > currently only support Debian based flavors such as Ubuntu. > > The main Issues here: > 1. NIC hot plugs: Ubuntu's ethX.cfg files looks different from ifcfg- >

[openstack-dev] [Neutron] Neutron-lib and Stadium evolution

Hi Neutrinos, As some of you may have noticed, since the merge of [1] you have now +2 rights on neutron-lib changes. Please make yourself familiar with review guidelines [2]: in general, code that targets the library should go through a much greater level of scrutiny and should be targeted if and

[openstack-dev] [craton] Developer weekly meeting scheduled every Thursday at 2100 UTC

Please join us for our weekly developer video conference call about Craton development every Thursday at 2100 UTC. We meet on Vidyo; please use this link: https://vc.rackspace.com/flex.html?roomdirect.html=OpmgbcmKWcXB31Tbl7VHgTrytb0 Meetings will be recorded and posted to YouTube, so if you do

Re: [openstack-dev] [lbaas][octavia] suggestion for today's meeting agenda: How to make the Amphora-agent support additional Linux flavors

Hi Greg, Thanks for the replay, comments inline. On Wed, Jun 29, 2016 at 9:59 PM, Gregory Haynes wrote: > On Wed, Jun 29, 2016, at 10:26 AM, Nir Magnezi wrote: > > Hello, > > Lately, I've been working on a fix[1] for the amhpora-agent, which > currently only support Debian

[openstack-dev] [security] [horizon] Security implications of exposing a keystone token to a JS client

Hello, vigilant folks of OpenStack Security team! The commit(s) I'd like you to take a look at introduces a new Horizon feature, Create (Glance) Image using CORS (AKA Cross-Origin Resource Sharing) [1]. The main idea is to bypass Horizon web-server when uploading large local image and to send it

[openstack-dev] [kolla] Continued support of Fedora as a base platform

Hi, Kolla has supported Fedora AFAIK since the project started, and offers several other valid options: # Valid options are [ centos, fedora, oraclelinux, ubuntu ] #kolla_base_distro: "centos" but in recent time, it came to my attention that the support of Fedora is lacking. There could be

[openstack-dev] [openstack-infra][nodepool] Can the nodes created by nodepool be reused by jenkins jobs?

Hi all, In OpenStack infra system after a job in Jenkins has finalized, Jenkins send a message called onFinalized to nodepool to delete the node. I have a question. Between the time the job is done and the node is deleted by nodepool, will the node be reused by other jobs in jenkins? All nodes

Re: [openstack-dev] [Nova] Questions about instance actions' update and finish

On 6/28/2016 7:28 AM, Andrew Laski wrote: On Tue, Jun 28, 2016, at 03:26 AM, Zhenyu Zheng wrote: Hi all, I'm working on add pagination and timestamp filter for os-instance-actions API: https://review.openstack.org/#/c/326326/ As Alex_xu pointed out that it will be better to filter by

Re: [openstack-dev] [Nova] Questions about instance actions' update and finish

On 6/29/2016 6:40 AM, Andrew Laski wrote: On Tue, Jun 28, 2016, at 09:27 PM, Zhenyu Zheng wrote: How about I sync updated_at and created_at in my patch, and leave the finish to the other BP, by this way, I can use updated_at for the timestamp filter I added and it don't need to change again

Re: [openstack-dev] [openstack-infra][nodepool] Can the nodes created by nodepool be reused by jenkins jobs?

On Thu, Jun 30, 2016 at 10:49:41AM +0800, 王华 wrote: > Hi all, > > In OpenStack infra system after a job in Jenkins has finalized, Jenkins > send a message called onFinalized to nodepool to delete the node. I have a > question. Between the time the job is done and > the node is deleted by

Re: [openstack-dev] [lbaas][octavia] suggestion for today's meeting agenda: How to make the Amphora-agent support additional Linux flavors

Like Doug said Amphora suppose to be a black box. It suppose to get some data - like info in /etc/defaults and do everything inside on its own. Everyone will be able to prepare his own implementation of this image without mixing things between each other. Lubosz Kosnik Cloud Software Engineer

Re: [openstack-dev] [openstack-infra][nodepool] Can the nodes created by nodepool be reused by jenkins jobs?

Hi Paul, There is a period between a job is done in Jenkins and the node is deleted by nodepool. Before the node is deleted, the node can be seen on Jenkins.How can Jenkins know not to use the node which has already run a job? Is there a mechanism to ensure this case? On Thu, Jun 30, 2016 at

Re: [openstack-dev] [Nova] Questions about instance actions' update and finish

On 6/29/2016 10:10 PM, Matt Riedemann wrote: On 6/29/2016 6:40 AM, Andrew Laski wrote: On Tue, Jun 28, 2016, at 09:27 PM, Zhenyu Zheng wrote: How about I sync updated_at and created_at in my patch, and leave the finish to the other BP, by this way, I can use updated_at for the timestamp

Re: [openstack-dev] [Nova] Questions about instance actions' update and finish

On Jun 29, 2016, at 10:05 PM, Matt Riedemann wrote: > >>> 2. The updated_at field is also empty, should we sync the updated_at >>> time to the created_at time when we create the action and also update >>> it whenever the action status changed, e.g finished. >> >>

Re: [openstack-dev] [constraints] Updating stable branch URL

On Tue, Jun 28, 2016 at 9:38 AM, Tony Breeds wrote: > On Mon, Jun 27, 2016 at 11:28:47PM +, Jeremy Stanley wrote: > >> I want to say there was a reason we were branching the requirements >> repo last, but now I can't remember what it is (or if we even did >> branch it

Re: [openstack-dev] [storlets] Docker images re-structuring

Hi Eran, Thank you for bringing up a great idea. > 1. Much easier to upgrade. > 2. Less time from fix to test. That's a big problem I experienced in my testing. Storlet agent should be managed by infra operator side, not by application developer side, as a part of infra software. It's a little

Re: [openstack-dev] [mistal] Mistral logo ideas?

> On 30 Jun 2016, at 00:12, Jason Rist wrote: > I was thinking of a tornado with eyes or a tasmanian devil. Both are wind > related. Thoughts? Jason, that would be cool to see :) Something like this IMO would be awesome, but as always in such cases, a particular

Re: [openstack-dev] [Nova][Neutron]What's the problem if there is no port status 'up' notification sent from neutron, while creating VM

The VM is paused until the 'up' notification to give the Neutron backend time to wire up the port. On Tue, Jun 28, 2016 at 7:59 PM, wrote: > Hi guys: > > As we know, nova will interacts with neutron for port creating and > configuration while creating VM. > > In the

Re: [openstack-dev] [octavia][upgrades] upgrade loadbalancer to new amphora image

Hi Ihar, thanks for starting this discussion. Comments in-line. After writing my comments in line, I might now realize that you're just talking about documenting a way for a user to do this, and not have Octavia handle it at all. If that's the case I apologize for my reading comprehension, but

[openstack-dev] [kolla] Build the docker images in a graceful way

Recently, Ansible release 2.1 version with lots of new feature. One of the interesting feature is the management for docker. Redhat also announced the Ansible Container project[0][1], which can build docker images by using Ansible Playbooks. No more write the ugly Dockerfile script. I think this

Re: [openstack-dev] Change in openstack/trove[master]: Ophaned Volume Not Removed on Instance Delete

Hi Kevin, There are a few blueprints in Trove that might address your use case. See https://blueprints.launchpad.net/trove/+spec/snapshot-as-backup-strategy or maybe https://blueprints.launchpad.net/trove/+spec/volume-delete-on-terminate . If neither is entirely correct, please feel free to

[openstack-dev] [kolla][keystone] is there chance the keystone cached the catalog and can not get the latest endpoints?

In Kolla CI, we see[1] publicURL endpoint for compute service not found this error for many times. The bug is here[0] After some debug, I found the endpoint is exist in the DB. But when running `nova service-list` It says `publicURL endpoint for compute service not found ​`​. After a few

Re: [openstack-dev] [Fuel][Plugins] Fuel Plugin Builder 4.1.0 released!

Hi, Great news, thanks! Regards, Michal > On 29 Jun 2016, at 14:28, Igor Kalnitsky wrote: > > Hey Fuelers, > > I'm glad to announce that FPB (fuel plugin builder) v4.1.0 has been > released on PyPI [1]. > > It's mostly a maintenance release without new features.

Re: [openstack-dev] Change in openstack/trove[master]: Ophaned Volume Not Removed on Instance Delete

Hi Will, Any time. ☺ If there is specific functionality that you think is missing and would like to see added to Trove, please enter a blueprint. Thanks! Peter From: Will Zhou [mailto:zzxw...@gmail.com] Sent: June-29-16 12:53 AM To: OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [Fuel][Plugins] Fuel Plugin Builder 4.1.0 released!

Wow! Thanks Igor for the update. Thanks & Regards, J. Venkata Mahesh -Original Message- From: Igor Kalnitsky [mailto:ikalnit...@mirantis.com] Sent: Wednesday, June 29, 2016 5:58 PM To: OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [kolla][keystone] is there chance the keystone cached the catalog and can not get the latest endpoints?

Hi, Looks like this bug is duplicate of https://bugs.launchpad.net/oslo.cache/+bug/1590779 HTH Best regards, Kairat Kushaev On Wed, Jun 29, 2016 at 3:32 PM, Jeffrey Zhang wrote: > In Kolla CI, we see[1] > > publicURL endpoint for compute service not found > > this

Re: [openstack-dev] [swift] Support for unicode filename in tempurl middleware

Hi Tim, thank you. I have modified my local python swift client according the diff on your patch and now I can generate tempURL on python2.7 too. I have noticed a bizzarre thing now. Trying to use CURL to download the generated tempURL, using a utf8 filename ("Monè.txt"), the download works fine

Re: [openstack-dev] [lbaas][octavia] suggestion for today's meeting agenda: How to make the Amphora-agent support additional Linux flavors

On Wed, Jun 29, 2016, at 02:18 PM, Nir Magnezi wrote: > Hi Greg, > > Thanks for the replay, comments inline. > > On Wed, Jun 29, 2016 at 9:59 PM, Gregory Haynes > wrote: >> __ >> On Wed, Jun 29, 2016, at 10:26 AM, Nir Magnezi wrote: >>> Hello, >>> >>> Lately, I've been

Re: [openstack-dev] [ironic] why do we need setting network driver per node?

On 06/29/2016 12:08 PM, Sam Betts (sambetts) wrote: My use case is supporting mixed hardware environments with hardware that has greater network capabilities and hardware without these capabilities without limiting my all my equipment to the lowest common feature set. The use case I’m describing

Re: [openstack-dev] [kolla] version of python2-oslo-config

2016-06-28 17:53 GMT+02:00 Steven Dake (stdake) : > The mitaka branch of Kolla requires 3.7 or later. > > Git checkout stable/mitaka > > Master may require 3.10, but that happens via the global requirements update > process, of which RDO will surely address in the future. > >

Re: [openstack-dev] [OpenStack-docs] [telemetry] Ceilometer and Aodh install guide(s)

Hi Andreas, Thanks for the clarification on this. We will consider the options. Best Regards, Ildikó > -Original Message- > From: Andreas Jaeger [mailto:a...@suse.com] > Sent: June 28, 2016 20:44 > To: Ildikó Váncsa; openstack-d...@lists.openstack.org > Cc:

Re: [openstack-dev] [ironic] why do we need setting network driver per node?

Dmitry thanks for rising this question! On Tue, Jun 28, 2016 at 6:32 PM, Dmitry Tantsur wrote: > Hi folks! > > I was reviewing https://review.openstack.org/317391 and realized I don't > quite understand why we want to have node.network_interface. What's the > real life use

Re: [openstack-dev] [craton] Developer weekly meeting scheduled every Thursday at 2100 UTC

-Original Message- From: Jim Baker Reply: OpenStack Development Mailing List (not for usage questions) Date: June 29, 2016 at 14:08:25 To: OpenStack Development Mailing List Subject: