Re: [openstack-dev] [Neutron] cloud-init IPv6 support

Neutron already offers a DNS server (within the DHCP namespace, I think). It does forward on non-local queries to an external DNS server, but it already serves local names for instances; we'd simply have to set one aside, or perhaps use one in a 'root' but nonlocal domain (metadata.openstack

Re: [openstack-dev] [Neutron] Port forwarding

Hi Gal, Congratulations, eventually you understand what I mean. Yes, in bulk. But I don't think that's an enhancement to the API. The bulk operation is more common scenario. It is more useful and covers the single port-mapping scenario. By the way, bulk operation may apply to a subnet, a

Re: [openstack-dev] [Openstack-dev] Devstack broken - third party CI broken

On Wed, 9 Sep 2015, Chris Dent wrote: On Wed, 9 Sep 2015, Chris Dent wrote: I'll push up a couple of reviews to fix this, either on the ceilometer or devstack side and we can choose which one we prefer. Here's the devstack fix: https://review.openstack.org/#/c/221634/ This is breaking

Re: [openstack-dev] [Openstack-dev] Devstack broken - third party CI broken

On Wed, 9 Sep 2015, Eduard Matei wrote: 2015-09-08 21:56:33.585 | Error: Service ceilometer-acentral is not running 2015-09-08 21:56:33.585 | + for service in '$failures' 2015-09-08 21:56:33.586 | ++ basename /opt/stack/status/stack/ceilometer-acompute.failure 2015-09-08 21:56:33.587 | +

Re: [openstack-dev] [Openstack-dev] Devstack broken - third party CI broken

You can work around the problem by replacing lines like: enable_service ceilometer-acompute ceilometer-acentral ceilometer-anotification ceilometer-collector ceilometer-api with: enable_plugin ceilometer git://git.openstack.org/openstack/ceilometer in your local.conf -- Chris Dent

Re: [openstack-dev] [Nova] What is the no_device flag for in block device mapping?

On Tue, Sep 08, 2015 at 05:32:29PM +, Murray, Paul (HP Cloud) wrote: > Hi All, > > I'm wondering what the "no_device" flag is used for in the block device > mappings. I had a dig around in the code but couldn't figure out why it > is there. The name suggests an obvious meaning, but I've

[openstack-dev] [Openstack-dev] Devstack broken - third party CI broken

Hi, Our Jenkins CI has been failing consistently last night during devstack install: 2015-09-08 21:56:33.585 | Error: Service ceilometer-acentral is not running 2015-09-08 21:56:33.585 | + for service in '$failures' 2015-09-08 21:56:33.586 | ++ basename

Re: [openstack-dev] [neutron] Fail to get ipv4 address from dhcp

Hi Zhi, Thanks very much for your help☺ Even turn off “ARP Spoofing” cannot work. But now, I find the cause for this: For ovs-agent-plugin, it wil loop to check OVS status and port status. But in my case, during the loop, it cannot detect there is new port added, so it fails to add tag for this

[openstack-dev] [sahara] FFE request for nfs-as-a-data-source

Hi, all. I would like to request FFE for nfs as a data source for sahara. This bp originally should include a dashboard change to create nfs as a data source. I will register it as another bp and implement it in next version. However, these patches have already done to put nfs-driver into

[openstack-dev] [tricircle]Weekly Team Meeting 2015.09.09

Hi Team, Let's resume our weekly meeting today. As Eran suggest before, we will mainly discuss the work we have now, and leave the design session in another time slot :) See you at UTC 1300 today. -- Zhipeng (Howard) Huang Standard Engineer IT Standard & Patent/IT Prooduct Line Huawei

Re: [openstack-dev] [Openstack-dev] Devstack broken - third party CI broken

Also, as I believe your CI is for Cinder, I recommend that you disable all uneeded services. (look how the DEVSTACK_LOCAL_CONFIG is used in devstack-gate to add the proper disable_service line). On Wed, Sep 9, 2015 at 11:00 AM, Chris Dent wrote: > On Wed, 9 Sep 2015, Chris

[openstack-dev] [Neutron][ML2] ML2 late/early-cycle sprint announcement

Folks, We are planning on having ML2 coding sprint on October 6 through 8, 2015. Some are calling it Liberty late-cycle sprint, others are calling it Mitaka early-cycle sprint. ML2 team has been discussing the issues related to synchronization of the Neutron DB resources with the back-end

Re: [openstack-dev] [Openstack-dev] Devstack broken - third party CI broken

On Wed, 9 Sep 2015, Chris Dent wrote: I'll push up a couple of reviews to fix this, either on the ceilometer or devstack side and we can choose which one we prefer. Here's the devstack fix: https://review.openstack.org/#/c/221634/ In discussion with other ceilometer cores we decided this was

Re: [openstack-dev] [nova] API v2.1 reference documentation

On 9 September 2015 at 03:43, Anne Gentle wrote: > > > On Tue, Sep 8, 2015 at 8:41 PM, Ken'ichi Ohmichi > wrote: >> >> Hi Melanie, >> >> 2015-09-09 8:00 GMT+09:00 melanie witt : >> > Hi All, >> > >> > With usage of v2.1

Re: [openstack-dev] [horizon] Concern about XStatic-bootswatch imports from fonts.googleapis.com

On 03/09/15 21:02, Matthias Runge wrote: > On 03/09/15 13:24, Thomas Goirand wrote: >> Hi, >> >> When doing: >> grep -r fonts.googleapis.com * >> >> there's 56 lines of this kind of result: >> xstatic/pkg/bootswatch/data/cyborg/bootstrap.css:@import >>

[openstack-dev] [TripleO] Releasing tripleo-common on PyPI

Hi, The tripleo-common library appears to be registered or PyPI but hasn't yet had a release[1]. I am not familiar with the release process - what do we need to do to make sure it is regularly released with other TripleO packages? We will also want to do something similar with the new

[openstack-dev] [Horizon] Feature Freeze Exception: shelving commands

Hi, I wanted to propose horizon-shelving-command[1][2] feature proposal for exception. This is a small feature based on existing pause/suspend command implementations. [1] https://blueprints.launchpad.net/horizon/+spec/horizon-shelving-command [2] https://review.openstack.org/220838

Re: [openstack-dev] [requirements] attention requirements-cores, please look out for constraints updates

> I'd like to add in a lower-constraints.txt set of pins and actually > start reporting on whether our lower bounds *work*. Do you have a spec in progress for lower-constraints.txt? It should help catch issues like https://review.openstack.org/221267 There are also lots of entries in

Re: [openstack-dev] [Fuel] Install fuel-libraryX.Y as a package on slave nodes

I disagree from the development point of view. Now I just change manifests on Fuel node and redeploy cluster to apply that changes. With your proposal I'll need to build a new package and add it to a repo every time I change something. On Tue, Sep 8, 2015 at 11:41 PM, Vladimir Kozhukalov <

Re: [openstack-dev] Should v2 compatibility mode (v2.0 on v2.1) fixes be applicable for v2.1 too?

On 09/08/2015 08:15 PM, Ken'ichi Ohmichi wrote: > 2015-09-08 19:45 GMT+09:00 Sean Dague : >> On 09/06/2015 11:15 PM, GHANSHYAM MANN wrote: >>> Hi All, >>> >>> As we all knows, api-paste.ini default setting for /v2 was >>> changed to run those on v2.1 (v2.0 on v2.1) which is really

Re: [openstack-dev] [Fuel][Plugins] request for update of fuel-plugin-builder on pypi

+1 to Simon Also the structure of fuel-plugin-builder should be refactored to community standards. everything in 'fuel_plugin_builder' directory should moved to top of repository. -- Best regards, Sergii Golovatiuk, Skype #golserge IRC #holser On Wed, Sep 9, 2015 at 12:25 PM, Simon Pasquier

Re: [openstack-dev] [murano][merlin] murano APIv2 and murano future ui

Hi Nikolay! Thanks for starting this activity! This is a really hot topic. We also used to have plan to migrate our API to pecan. [1] This also can be discussed. Do we have a blueprint for that? Could you please file it and attach etherpad to a new blueprint. [1] -

Re: [openstack-dev] [murano][merlin] murano APIv2 and murano future ui

Please note that some projects already using pecan+WSME are actually thinking about finding something else, since WSME doesn't have much activity and has its fair share of issues. If you missed it, check out this conversation thread:

[openstack-dev] [murano][merlin] murano APIv2 and murano future ui

Hi all, Yesterday on IRC weekly meeting murano team decided to start collecting ideas about murano APIv2 and murano future ui. We have to etherpads for this purpose: 1) https://etherpad.openstack.org/p/murano-APIv2 - for murano API v2 ideas 2)

Re: [openstack-dev] [murano] Proposing Nikolai Starodubtsev for core

+1 On 09/08/2015 02:28 PM, Stan Lagun wrote: +1 Sincerely yours, Stan Lagun Principal Software Engineer @ Mirantis On Tue, Sep 1, 2015 at 3:03 PM, Alexander Tivelkov > wrote: +1. Well deserved. -- Regards, Alexander

[openstack-dev] [nova] [all] Updated String Freeze Guidelines

Hi, I have had quite a few comments from folks about the string freeze being too strict. It was noted that: * users will prefer an untranslated log, over a silent failure * translators don't want existing strings changing while they are translating them * translators tooling can cope OK with

Re: [openstack-dev] [aodh][ceilometer] (re)introducing Aodh - OpenStack Alarming

Hi, Gord, Good to know there will be a team dedicated to this alarming service. After reading your email, I still feel a need for some clarifications. - According to [1], Aodh will be released as a standalone service, am I understanding this correctly? - What is the official name for this new

Re: [openstack-dev] [TripleO] Releasing tripleo-common on PyPI

On 09/09/2015 12:15 PM, Dougal Matthews wrote: Hi, The tripleo-common library appears to be registered or PyPI but hasn't yet had a release[1]. I am not familiar with the release process - what do we need to do to make sure it is regularly released with other TripleO packages? I think this is

Re: [openstack-dev] [Openstack-dev] Devstack broken - third party CI broken

Line export DEVSTACK_LOCAL_CONFIG="disable_service ceilometer-acompute ceilometer-acentral ceilometer-collector ceilometer-api" in the job config did the trick. Thanks, Eduard __ OpenStack Development Mailing List (not for

Re: [openstack-dev] [Fuel][Plugins] request for update of fuel-plugin-builder on pypi

+2 to sergii and btw create dedicated repos for plugin examples On Wed, Sep 9, 2015 at 12:34 PM, Sergii Golovatiuk wrote: > +1 to Simon > > Also the structure of fuel-plugin-builder should be refactored to > community standards. everything in 'fuel_plugin_builder'

[openstack-dev] [mistral] Mistral Liberty-3 milestone has been released

Hi, Mistral Liberty 3 milestone has been released! We’ve also released Mistral Client 1.0.2 that has some adjustments needed to use the new Mistral server. Below are corresponding release pages where you can find downloadable artefacts and more detailed information about what has changed:

Re: [openstack-dev] [Fuel] Install fuel-libraryX.Y as a package on slave nodes

Vladimir, thanks for bringing this up. It greatly correlates with the idea of modularity. Everything related to an openstack release should be put in one place and should be managed as a solid bundle on the master node. Package repository is the first solution that comes to the mind and it looks

[openstack-dev] [Fuel][Plugins] request for update of fuel-plugin-builder on pypi

Hi, It would be cool if fuel-plugin-builder (fpb) v3.0.0 could be released on pypi. We've moved some of the LMA plugins to use the v3 format. Right now we have to install fpb from source which is hard to automate in our tests unfortunately (as already noted by Sergii [1]). BR, Simon [1]

Re: [openstack-dev] [murano][merlin] murano APIv2 and murano future ui

Kate, This bp is pretty old, but I think it suits our needs [1]. Yeah, I'll attach etherpads to it. The idea about pecan/wsme is really useful. [1]: https://blueprints.launchpad.net/murano/+spec/api-vnext Nikolay Starodubtsev Software Engineer Mirantis Inc. Skype: dark_harlequine1

Re: [openstack-dev] [Neutron][ML2] ML2 late/early-cycle sprint announcement

Hi Sukhdev, The common sync framework is something i was also thinking about for some time now. I think its a very good idea and would love if i could participate in the talks (and hopefully the implementation as well) Thanks Gal. On Wed, Sep 9, 2015 at 9:46 AM, Sukhdev Kapur

[openstack-dev] [Fuel] 7.0 Release - Hard Code Freeze in action

Hello everyone, Please be informed that Hard Code Freeze for Fuel 7.0 Release is officially in action and the following changes have been applied: 1. Stable/7.0 branch was created for the following repos: fuel-main fuel-library fuel-web fuel-ostf fuel-astute fuel-qa python-fuelclient

Re: [openstack-dev] [Fuel] Install fuel-libraryX.Y as a package on slave nodes

I agree that we shouldn't need to sync as we should be able to just update the fuel-library package. That being said, I think there might be a few issues with this method. The first issue is with plugins and how to properly handle the distribution of the plugins as they may also include puppet

Re: [openstack-dev] [Heat] Multi Node Stack - keystone federation

On 09/09/15 04:10, SHTILMAN, Tomer (Tomer) wrote: On 07/09/15 05:27, SHTILMAN, Tomer (Tomer) wrote: Hi Currently in heat we have the ability to deploy a remote stack on a different region using OS::Heat::Stack and region_name in the context My question is regarding multi node , separate

Re: [openstack-dev] [murano][merlin] murano APIv2 and murano future ui

thanks, Stéphane. It's a good notice. Nikolay Starodubtsev Software Engineer Mirantis Inc. Skype: dark_harlequine1 2015-09-09 15:10 GMT+03:00 Stéphane Bisinger : > Please note that some projects already using pecan+WSME are actually > thinking about finding

Re: [openstack-dev] Should v2 compatibility mode (v2.0 on v2.1) fixes be applicable for v2.1 too?

> 在 2015年9月8日，下午6:45，Sean Dague 写道： > > On 09/06/2015 11:15 PM, GHANSHYAM MANN wrote: >> Hi All, >> >> As we all knows, api-paste.ini default setting for /v2 was changed to >> run those on v2.1 (v2.0 on v2.1) which is really great think for easy >> code maintenance in future

Re: [openstack-dev] [tricircle]Weekly Team Meeting 2015.09.09

Hi Please find the meetbot log at http://eavesdrop.openstack.org/meetings/tricircle/2015/tricircle.2015-09-09-13.01.html . And also a noise cancelled minutes in the attachment. On Wed, Sep 9, 2015 at 4:22 PM, Zhipeng Huang wrote: > Hi Team, > > Let's resume our weekly

Re: [openstack-dev] [aodh][ceilometer] (re)introducing Aodh - OpenStack Alarming

On Wed, Sep 09 2015, Qiming Teng wrote: > - According to [1], Aodh will be released as a standalone service, > am I understanding this correctly? Yes. > - What is the official name for this new serivce when it stands on its > own feet: "Telemetry Alarming" or just "Alarming" or something

Re: [openstack-dev] [TripleO] trello

On 08/09/15 16:36, Derek Higgins wrote: Hi All, Some of ye may remember some time ago we used to organize TripleO based jobs/tasks on a trello board[1], at some stage this board fell out of use (the exact reason I can't put my finger on). This morning I was putting a list of things

Re: [openstack-dev] [tripleo] Plugin integration and environment file naming

Looks good to me. Rob On 9/8/15, 4:40 AM, "Steven Hardy" wrote: >Hi all, > >So, lately we're seeing an increasing number of patches adding integration >for various third-party plugins, such as different neutron and cinder >backends. > >This is great to see, but it also

Re: [openstack-dev] [Fuel] Install fuel-libraryX.Y as a package on slave nodes

Andrey, This change is going to make things even easier. Currently you don't need to build fuel-library package manually, Perestroika is going to do it for you. It builds necessary packages during minutes for every review request and packaging ci even tests it for you. You just need to make

Re: [openstack-dev] [Fuel] Install fuel-libraryX.Y as a package on slave nodes

I don't think juggling with repos and pull requests is easier than direct editing of files on Fuel node. Do we have Perestorika installed on Fuel node in 7.0? On Wed, Sep 9, 2015 at 3:47 PM, Vladimir Kozhukalov < vkozhuka...@mirantis.com> wrote: > Andrey, > > This change is going to make things

Re: [openstack-dev] [Barbican] Nominating Dave Mccowan for Barbican core

+1 Dave is a great member of the team, and I think he has earned it. -Nate On Tue, Sep 8, 2015 at 12:13 PM, Douglas Mendizábal < douglas.mendiza...@rackspace.com> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > +1 > > Dave has been a great asset to the team, and I think he would

Re: [openstack-dev] [nova] CI for reliable live-migration

Hello, Update for gate-tempest-dsvm-multinode-full job. Here is top 12 failing tests in weekly period: tempest.api.compute.servers.test_disk_config.ServerDiskConfigTestJSON.test_resize_server_from_manual_to_auto: 14

Re: [openstack-dev] [Fuel] Install fuel-libraryX.Y as a package on slave nodes

No, Perestroika is not available on the Fuel master node and it is not going to be available in the future. But Perestroika is going to be re-worked so as to make it is possible to used separately from CI. It is gonna be a python application to make package building as easy for a developer/user as

Re: [openstack-dev] [Fuel][Plugins] request for update of fuel-plugin-builder on pypi

Hi guys, I'm going to wait for the patch [1] and then make a FPB release. Regarding repo restructuring.. We do have an issue, and IIRC it's targeted to 8.0. [1]: https://review.openstack.org/#/c/221434/ Thanks, Igor On Wed, Sep 9, 2015 at 2:23 PM, Swann Croiset wrote:

Re: [openstack-dev] [Fuel] Install fuel-libraryX.Y as a package on slave nodes

Alex, Regarding plugins: plugins are welcome to install specific additional DEB/RPM repos on the master node, or just configure cluster to use additional onl?ne repos, where all necessary packages (including plugin specific puppet manifests) are to be available. Current granular deployment

Re: [openstack-dev] [Fuel] Install fuel-libraryX.Y as a package on slave nodes

Andrey, you have highlighted important case. I hope you agree that this case is not a blocker for the proposal. From the developer's point of view packages are awful and we should use raw git repos on every node. It could make developer's life way easier. But from architecture perspective it would

[openstack-dev] [neutron][nova] QoS Neutron-Nova integration

Hi, Looking forward to the M cycle, I was wondering if we could loop you in our next week Neutron/QoS meeting on #openstack-meeting-3 around 16:00 CEST Sept 16th. We're thinking about several ways we should integrate QoS between nova and the new extendable QoS service on

Re: [openstack-dev] [Fuel] Install fuel-libraryX.Y as a package on slave nodes

Hey Vladimir, > Regarding plugins: plugins are welcome to install specific additional > DEB/RPM repos on the master node, or just configure cluster to use > additional onl?ne repos, where all necessary packages (including plugin > specific puppet manifests) are to be available. Current granular

Re: [openstack-dev] [neutron][nova] QoS Neutron-Nova integration

Hi Ajo, I am In. Thanks for the information. Thanks Vikram On Wed, Sep 9, 2015 at 8:05 PM, Miguel Angel Ajo wrote: > >Hi, > > Looking forward to the M cycle, > > I was wondering if we could loop you in our next week Neutron/QoS > meeting > on

[openstack-dev] [glance] [nova] Verification of glance images before boot

How can I know that the image that a new instance is spawned from - is actually the image that was originally registered in glance - and has not been maliciously tampered with in some way? Is there some kind of verification that is performed against the md5sum of the registered image in

Re: [openstack-dev] [tripleo] Upgrades, Releases & Branches

On Tue, Aug 18, 2015 at 02:28:39PM -0400, James Slagle wrote: > On Tue, Aug 18, 2015 at 2:10 PM, Steven Hardy wrote: > > On Mon, Aug 17, 2015 at 03:29:07PM -0400, James Slagle wrote: > >> On Mon, Aug 17, 2015 at 9:28 AM, Steven Hardy wrote: > >> > Hi all, >

Re: [openstack-dev] [tripleo] Upgrade plans for RDO Manager - Brainstorming

On 24/08/15 15:12, Emilien Macchi wrote: Hi, So I've been working on OpenStack deployments for 4 years now and so far RDO Manager is the second installer -after SpinalStack [1]- I'm working on. SpinalStack already had interested features [2] that allowed us to upgrade our customer platforms

Re: [openstack-dev] OpenStack support for Amazon Concepts - was Re: cloud-init IPv6 support

And here is the code that does this (for cloudinit 0.7.x): https://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/cloudinit/sources/helpers/openstack.py This same code is used by the config drive datasource (the one that makes a disk/iso) in cloudinit and the http endpoint

Re: [openstack-dev] [Fuel] Nominate Andrey Sledzinskiy for fuel-ostf core

+1 8 сент. 2015 г. 13:07 пользователь "Alexander Kostrikov" < akostri...@mirantis.com> написал: > +1 > > On Tue, Sep 8, 2015 at 9:07 AM, Dmitriy Shulyak > wrote: > >> +1 >> >> On Tue, Sep 8, 2015 at 9:02 AM, Anastasia Urlapova < >> aurlap...@mirantis.com> wrote: >> >>> +1

Re: [openstack-dev] [Neutron] cloud-init IPv6 support

I think the DNS idea's going to run into problems for tenants that want to run their own, or have existing DNS servers. It may not play nicely with Designate as well. Kevin From: Ian Wells [ijw.ubu...@cack.org.uk] Sent: Wednesday, September 09, 2015 12:17 AM

Re: [openstack-dev] [Fuel] Remove MOS DEB repo from master node

Hey Vladimir, > > The idea is to remove MOS DEB repo from the Fuel master node by default > and use online MOS repo instead. Pros of such an approach are: > > 0) Reduced requirement for the master node minimal disk space > Is this a problem? How much disk space is saved If I have to go create a

Re: [openstack-dev] [all] Something about being a PTL

Beautiful summary, Flavio, especially the points about creating new PTL's. It's the bus-number argument: How many people have to get hit by a bus for the project to falter? It's best to have a backup. Also: Being a PTL is a full-time job. >From working with current and former PTL's, I've noticed

Re: [openstack-dev] [Barbican] Nominating Dave Mccowan for Barbican core

i'm not a core, but +1 from me. Dave has made solid contributions and would be a great addition to the core team. mike On 09/08/2015 12:05 PM, Juan Antonio Osorio wrote: I'd like to nominate Dave Mccowan for the Barbican core review team. He has been an active contributor both in doing

Re: [openstack-dev] [glance] [nova] Verification of glance images before boot

That's correct. The size and the checksum are to be verified outside of Glance, in this case Nova. However, you may want to note that it's not necessary that all Nova virt drivers would use py-glanceclient so you would want to check the download specific code in the virt driver your Nova

[openstack-dev] [nova][qa] Microsoft Hyper-V CI removed from nova-ci group until fixed

I noticed hyper-v CI reporting a +1 on a change [1] that actually failed with a bad looking merge conflict, so I've removed the hyper-v CI account from the nova-ci group in Gerrit [2]. From talking with ociuhandu it sounds like zuul issues and they are working on it. Ping me or John when

Re: [openstack-dev] [Fuel] Remove MOS DEB repo from master node

We thought about doing this as well and opted for a local repo, at least for now. If you want to offer an online repo, I think it could be useful to allow either scenario. Just a thought from your friendly neighbors here. ; ) /adam On Sep 8, 2015 7:03 AM, "Vladimir Kozhukalov"

Re: [openstack-dev] [all] Something about being a PTL

Very well said. Thank you for this. Kevin From: Flavio Percoco [fla...@redhat.com] Sent: Wednesday, September 09, 2015 8:10 AM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [all] Something about being a PTL Greetings, Next week many

[openstack-dev] [Sahara] FFE request for improved secret storage

hi all, i am requesting an FFE for the improved secret storage feature. this change will allow operators to utilize the key manager service for offloading the passwords stored by sahara. this change does not implement mandatory usage of barbican, and defaults to a backward compatible

[openstack-dev] [all] Something about being a PTL

Greetings, Next week many folks will be running for PTL positions and I thought about taking the time to dump[0] some thoughts about what being a PTL means - at least for me - and what one should consider before running. Since the audience I want to reach is mostly in this mailing list, I

Re: [openstack-dev] [glance] [nova] Verification of glance images before boot

The glance client (running 'inside' the Nova server) will re-calculate the checksum as it downloads the image and then compare it against the expected value. If they don't match an error will be raised. How can I know that the image that a new instance is spawned from - is actually the image

[openstack-dev] [glance] differences between def detail() and def index() in glance/registry/api/v1/images.py

Hello, I am hitting an error and its trace passes def index () in glance/registry/api/v1/images.py. I assume def index() is called by glance image-list. However, while testing glance image-list I realized that def detail() is called under glance/registry/api/v1/images.py instead of def index().

Re: [openstack-dev] [ironic] [tripleo] [kolla] Possible to support multiple compute drivers?

I'd greatly prefer using availability zones/host aggregates as I'm trying to keep the footprint as small as possible. It does appear that in the section "configure scheduler to support host aggregates" [1], that I can configure filtering using just one scheduler (right?). However, perhaps more

Re: [openstack-dev] [TripleO] Releasing tripleo-common on PyPI

On 09/09/2015 12:54 PM, Doug Hellmann wrote: > Excerpts from Dmitry Tantsur's message of 2015-09-09 12:58:04 +0200: >> On 09/09/2015 12:15 PM, Dougal Matthews wrote: >>> Hi, >>> >>> The tripleo-common library appears to be registered or PyPI but hasn't yet >>> had >>> a release[1]. I am not

Re: [openstack-dev] [rootwrap] rootwrap and libraries - RFC

Excerpts from Matt Riedemann's message of 2015-09-09 13:45:29 -0500: > > On 9/9/2015 1:04 PM, Doug Hellmann wrote: > > Excerpts from Sean Dague's message of 2015-09-09 13:36:37 -0400: > >> We've got a new pattern emerging where some of the key functionality in > >> services is moving into

Re: [openstack-dev] [glance] differences between def detail() and def index() in glance/registry/api/v1/images.py

I assume you're using Glance client, if so, by default, when you issuing command 'glance image-list', it will call /v1/images/detail instead of /v1/images, you can use curl or any browser http client to see the difference. Basically, just like the endpoint name, /v1/images/detail will give you

Re: [openstack-dev] [all] Base feature deprecation policy

On 10 September 2015 at 06:18, Doug Hellmann wrote: > Excerpts from Ben Swartzlander's message of 2015-09-08 22:22:38 -0400: >> It would be a recognition that most customers don't want to upgrade >> every 6 months -- they want to skip over 3 releases and upgrade every 2 >>

Re: [openstack-dev] [requirements] attention requirements-cores, please look out for constraints updates

On 9 September 2015 at 22:22, Alan Pevec wrote: >> I'd like to add in a lower-constraints.txt set of pins and actually >> start reporting on whether our lower bounds *work*. > > Do you have a spec in progress for lower-constraints.txt? > It should help catch issues like

Re: [openstack-dev] [neutron] port delete allowed on VM

This is expected behavior. On Tue, Sep 8, 2015 at 12:58 PM, Ajay Kalambur (akalambu) < akala...@cisco.com> wrote: > Hi > Today when we create a VM on a port and delete that port I don’t get a > message saying Port in Use > > Is there a plan to fix this or is this expected behavior in neutron > >

[openstack-dev] [openstack-operators][chef] Pre-release of new kitchen-openstack driver, Windows and 1.4 test-kitchen support

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Everyone! I'd like to announce a pre-release[1] of 2.0.0.dev of the kitchen-openstack[2] driver gem. I've been able to test this with Windows 2012R2 and all the flavors of Linux I have on my OpenStack Cloud, but would love some more

[openstack-dev] [Ironic] Summit session brainstorming

Hi all, I don't have an exact schedule or anything, but I wanted to start brainstorming topics for the summit. I've started an etherpad: https://etherpad.openstack.org/p/mitaka-ironic-design-summit-ideas Keep in mind these should be topics that we need to sort things out on - let's be sure not

Re: [openstack-dev] [Fuel] Remove MOS DEB repo from master node

On Thu, Sep 10, 2015 at 3:29 AM, Alex Schultz wrote: > > Hey Vladimir, > > >> >> >>> 1) There won't be such things in like [1] and [2], thus less complicated flow, less errors, easier to maintain, easier to understand, easier to troubleshoot 2) If one wants

Re: [openstack-dev] [magnum] keystone pluggable model

- Original Message - > From: "Murali Allada" > To: "OpenStack Development Mailing List (not for usage questions)" > > Sent: Thursday, 10 September, 2015 6:41:40 AM > Subject: [openstack-dev] [magnum] keystone pluggable

[openstack-dev] [all] Election Season, PTL and TC September/October 2015

PTL Election details: https://wiki.openstack.org/wiki/PTL_Elections_September_2015 TC Election details: https://wiki.openstack.org/wiki/TC_Elections_September/October_2015 Please read the stipulations and timelines for candidates and electorate contained in these wikipages. There will be an

Re: [openstack-dev] [ironic] [tripleo] [kolla] Possible to support multiple compute drivers?

- Original Message - > From: "Jeff Peeler" > To: "OpenStack Development Mailing List (not for usage questions)" > > > I'd greatly prefer using availability zones/host aggregates as I'm trying > to keep the footprint as small as

Re: [openstack-dev] [Glance] Feature Freeze Exception proposal

FYI, this was granted FFE. On 9/8/15 11:02 AM, Nikhil Komawar wrote: > Malini, > > Your note on the etherpad [1] went unnoticed as we had that sync on > Friday outside of our regular meeting and weekly meeting agenda etherpad > was not fit for discussion purposes. > > It would be nice if you all

[openstack-dev] SOS

Hi: I need a coreos image that supports kubernetes , without it , my boss will kick my arse.__ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [puppet]Fwd: Delorean with CBS Liberty deps repos

I'll make the changes this week and test if our CI pass. Forwarded Message Subject: Delorean with CBS Liberty deps repos Date: Thu, 10 Sep 2015 02:22:24 +0200 From: Alan Pevec To: Emilien Macchi CC: Matthias Runge ,

Re: [openstack-dev] SOS

It should be easy, you google it for coreos raw or qcow2 image then import it into openstack Sent from my iPhone > On 2015年9月10日, at 10:53, 蒋吉 wrote: > > Hi: > I need a coreos image that supports kubernetes , without it , my boss > will kick my arse. > > > > >

Re: [openstack-dev] SOS

I haven't tried it out, but hope this blog could save you arse. https://www.cloudssky.com/en/blog/Kubernetes-on-CoreOS-with-OpenStack/ http://stable.release.core-os.net/amd64-usr/367.1.0/coreos_production_openstack_image.img.bz2 On 09/09/2015 07:53 PM, 蒋吉 wrote: Hi: I need a coreos

Re: [openstack-dev] [tricircle]Weekly Team Meeting 2015.09.09

Let’s also start the PTL selection according to the guide of OpenStack: https://wiki.openstack.org/wiki/PTL_Elections_September_2015 Please submit your PTL candidacy according to : https://wiki.openstack.org/wiki/PTL_Elections_September_2015#How_to_submit_your_candidacy Best Regards Chaoyi

[openstack-dev] [neutron] RFE process question

Greetings Devs, I'm very excited about the new RFE process and thought I'd test it by requesting a feature that is very often requested by my users[1]. There are some great docs out there about how to submit an RFE, but I don't know what should happen after the submission to launchpad. My RFE

Re: [openstack-dev] [Fuel] Remove MOS DEB repo from master node

Hello, I agree with Vladimir - the idea of online repos is a right way to move. In 2015 I believe we can ignore this "poor Internet connection" reason, and simplify both Fuel and UX. Moreover, take a look at Linux distributives - most of them fetch needed packages from the Internet during

Re: [openstack-dev] [rootwrap] rootwrap and libraries - RFC

On 10 September 2015 at 06:45, Matt Riedemann wrote: > > The problem with the static file paths in rootwrap.conf is that we don't > know where those other library filter files are going to end up on the > system when the library is installed. We could hard-code

[openstack-dev] [Tacker][NFV] Proposal for experimental features

Folks: We are gathering momentum in our activities towards building a VNFM / NFVO in OpenStack Tacker project [1]. As discussed in the last week's irc meeting [2], I'd like to propose few "experimental features" within Tacker. It is well know practice to use experimental tag to introduce

Re: [openstack-dev] [ironic] [tripleo] [kolla] Possible to support multiple compute drivers?

On Wed, Sep 02, 2015 at 03:42:20PM -0400, Jeff Peeler wrote: > Hi folks, > > I'm currently looking at supporting Ironic in the Kolla project [1], but > was unsure if it would be possible to run separate instances of nova > compute and controller (and scheduler too?) to enable both baremetal and >

Re: [openstack-dev] [rootwrap] rootwrap and libraries - RFC

Excerpts from Sean Dague's message of 2015-09-09 13:36:37 -0400: > We've got a new pattern emerging where some of the key functionality in > services is moving into libraries that can be called from different > services. A good instance of this is os-brick, which has the setup / > config

Re: [openstack-dev] [all] Base feature deprecation policy

Excerpts from Ben Swartzlander's message of 2015-09-08 22:22:38 -0400: > On 09/08/2015 01:58 PM, Doug Hellmann wrote: > > Excerpts from Ben Swartzlander's message of 2015-09-08 13:32:58 -0400: > >> On 09/03/2015 08:22 AM, Thierry Carrez wrote: > >>> Hi everyone, > >>> > >>> A feature deprecation

Re: [openstack-dev] [rootwrap] rootwrap and libraries - RFC

On 9/9/2015 1:04 PM, Doug Hellmann wrote: Excerpts from Sean Dague's message of 2015-09-09 13:36:37 -0400: We've got a new pattern emerging where some of the key functionality in services is moving into libraries that can be called from different services. A good instance of this is os-brick,

[openstack-dev] [magnum] keystone pluggable model

?Hi All, In the IRC meeting yesterday, I brought up this new blueprint I opened. https://blueprints.launchpad.net/magnum/+spec/pluggable-keystone-model? The goal of this blueprint is to allow magnum operators to integrate with their version of keystone easily with downstream patches. The

  1   2   >