Re: [openstack-dev] [trove] Upcoming specs and blueprints for Trove/Mitaka

On 10/12/15 18:44 +, Vyvial, Craig wrote: Amrith/Victoria, Thanks for the heads up about this these blueprints for the Mitaka cycle. This looks like a lot of work but there shouldn’t be a reason to hold back new blueprints this early in the cycle if they plan on being completed in Mitaka.

[openstack-dev] Cleaning Up Deprecation Warnings in the Gate

Hi Everyone, So we were having a discussion in #openstack-qa about the amount of logs we have to process in our elastic search cluster and that we frequently have issues with the amount of RAM available in the cluster. In general, it would be good for projects to take a look at how verbose their

Re: [openstack-dev] [trove] Upcoming specs and blueprints for Trove/Mitaka

2015-12-10 13:10 GMT-03:00 Amrith Kumar : > Members of the Trove community, > > Over the past couple of weeks we have discussed the possibility of an > early deadline for submission of trove specifications for projects that are > to be included in the Mitaka release. I

Re: [openstack-dev] Reg: Blueprint -- add-compute-node-on-the-go

Excerpts from Atul Ag's message of 2015-12-10 06:50:05 -0800: > Hi, > > I have added the blue print > https://blueprints.launchpad.net/nova/+spec/add-compute-node-on-the-go. > Can you please let me know the feasibility, and accept the blueprint. > Hi Atul, welcome, and thanks for your

Re: [openstack-dev] [oslo][all] The lock files saga (and where we can go from here)

Unsure what u mean here, Tooz is already in oslo. Where u thinking of something else? D'Angelo, Scott wrote: Could the work for the tooz variant be leveraged to add a truly distributed solution (with the proper tooz distributed backend)? IF so, then +1 to this idea. Cinder will be

Re: [openstack-dev] Cleaning Up Deprecation Warnings in the Gate

On 10/12/15 12:04 PM, Matthew Treinish wrote: Using this query to see how many deprecation warning we emit on jobs running on master in the past 7 days:

[openstack-dev] [Fuel] Multiple repos UX

Dear colleagues, At the moment we have several places where we configure multiple rpm/deb repositories. Those are: 1. Web UI (cluster settings tab) where we define repos for cluster deployment 2. Fuel-menu (bootstrap section) where we define repos for building ubuntu bootstrap image

Re: [openstack-dev] [trove] Upcoming specs and blueprints for Trove/Mitaka

Flavio, So we had a quite a few specs in the last cycle that were rushed to be approved and then code rushed as well. This was meant to make sure that would not happen again because it ended up hurting us and had to get many of features through with exceptions. This is by no means a hard spec

Re: [openstack-dev] [trove] Upcoming specs and blueprints for Trove/Mitaka

Flavio, The issue we had in the last cycle was that a lot of specs and code arrived for review late in the process and this posed a challenge. The intent this time around was to ensure that there wasn't such a back-end loaded process and that people had a good idea of what is coming down the

[openstack-dev] [infra][release][all] Automatic .ics generation for OpenStack's and project's deadlines

Greetings, I'd like to explore the possibility of having .ics generated - pretty much the same way we generate it for irc-meetings - for the OpenStack release schedule and project's deadlines. I believe just 1 calendar would be enough but I'd be ok w/ a per-project .ics too. With the new

Re: [openstack-dev] [infra][release][all] Automatic .ics generation for OpenStack's and project's deadlines

On 2015-12-10 18:20:44 + (+), Flavio Percoco wrote: > I'd like to explore the possibility of having .ics generated - pretty > much the same way we generate it for irc-meetings - for the OpenStack > release schedule and project's deadlines. I believe just 1 calendar > would be enough but

Re: [openstack-dev] [nova] Testing concerns around boot from UEFI spec

> -Original Message- > From: Sean Dague [mailto:s...@dague.net] > Sent: Friday, December 4, 2015 9:47 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [nova] Testing concerns around boot from UEFI > spec > > On 12/04/2015 08:34 AM, Daniel P. Berrange wrote: > >

Re: [openstack-dev] [mistral] Improving Mistral pep8 rules files to match Mistral guidelines

Thanks, Anastasia! Who can take start documenting the rules? I remember only a few rules and I don’t know all the nuances. For example, if the return statement is the only statement of a function – do you still need a blank line before it? Once the rules doc will be available I can work on

Re: [openstack-dev] [cinder] Dependencies of snapshots on volumes

On 10 December 2015 at 04:48, Li, Xiaoyan wrote: > > This leads to a problem like extending volume. Extending a volume in an > incremental snapshot fails > in vendor storage. And then the cinder volume goes into error_extending > status. From my opinion this is not good. >

[openstack-dev] neutron metadata-agent HA

Hi, I've installed Kilo release of OpenStack. An interesting thing, for us, is the new high available Neutron L3 agent, which - as far as I understand - can be set in active/active mode. But I verified what is reported in the HA Guide

[openstack-dev] [openstack-infra] Using Neutron client in the gate

Hello All, I would like to run some "fullstack" integration tests for Kuryr and run them in the gate. For the tests i would like to use the Neutron client for communicating with the working devstack Neutron service. What is the best way to instantiate the client in terms of auth_url and

Re: [openstack-dev] [Fuel] Feature Freeze Exceptions

Update after today's IRC meeting [1]: [1] http://eavesdrop.openstack.org/meetings/fuel/2015/fuel.2015-12-10-16.00.html 1. [MERGED] CentOS 7. ETA: Monday 7th. Blueprint: https://blueprints.launchpad.net/fuel/+spec/master-on-centos7. 2. [MOVED to 9.0] Disable queue mirroring for RPC

Re: [openstack-dev] [openstack-ansible] Mid Cycle Sprint

I'd be game to join in if it's in San Antonio. While I'd love to go to London I don't think I'd make. Like Major I'd like to see some doc work. Amy Marrich From: Jesse Pretorius Sent: Wednesday, December 9, 2015 6:45:56 AM To:

[openstack-dev] [magnum] Containerize Flannel/Etcd

All, As a follow-on from today's networking subteam meeting, I received additional feedback from the Kubernetes community about running Etcd and Flannel in a container. Etcd/Flannel were containerized to simply the N different ways that these services can be deployed. It simplifies Kubernetes

Re: [openstack-dev] Mitaka Infra Sprint

On Thu, Dec 10, 2015 at 3:24 AM, Joshua Hesketh wrote: > Location: > HPE Fort Collins Colorado Office Thanks Josh, I've confirmed the address and building number: Hewlett-Packard Enterprise - Building 6 3404 E Harmony Road Fort Collins, CO, 80528 Wiki has also been

Re: [openstack-dev] [mistral] bugfix for "Fix concurrency issues by using READ_COMMITTED" unveils / creates a different bug

Excerpts from ELISHA, Moshe (Moshe)'s message of 2015-12-07 08:29:44 -0800: > Hi all, > > The current bugfix I am working on[1] have unveiled / created a bug. > Test "WorkflowResumeTest.test_resume_different_task_states" sometimes fails > because "task4" is executed twice instead of once (See

Re: [openstack-dev] Cleaning Up Deprecation Warnings in the Gate

On Thu, Dec 10, 2015 at 03:03:01PM -0500, gord chung wrote: > > > On 10/12/15 12:04 PM, Matthew Treinish wrote: > >Using this query to see how many deprecation warning we emit on jobs running > >on > >master in the past 7 days: > > >

Re: [openstack-dev] Mesos Conductor using container-create operations

I think extending the container object to Mesos via command like container-create is a fine idea. Going into details, however, we run into some complication. 1. The user would still have to choose a DSL to express the container. This would have to be a kube and/or swarm DSL since we don't want to

Re: [openstack-dev] [Kuryr] Testing, Rally and Wiki

Hi Gal, > We are also working on combining Rally testing with Kuryr and for that we > are going to > introduce Docker context plugin and client and other parts that are > probably needed by other projects (like Magnum) > I think it would be great if we can combine forces on this. What this

Re: [openstack-dev] [Ironic] [Nova] continuing the "multiple compute host" discussion

On Thu, Dec 10, 2015 at 03:57:59PM -0800, Devananda van der Veen wrote: > All, > > I'm going to attempt to summarize a discussion that's been going on for > over a year now, and still remains unresolved. > > TLDR; > > > The main touch-point between Nova and Ironic continues to be a

[openstack-dev] [Ironic] [Nova] continuing the "multiple compute host" discussion

All, I'm going to attempt to summarize a discussion that's been going on for over a year now, and still remains unresolved. TLDR; The main touch-point between Nova and Ironic continues to be a pain point, and despite many discussions between the teams over the last year resulting in a

Re: [openstack-dev] [QA][Tempest] Drop javelin off tempest

On Thu, 10 Dec 2015, Daniel Mellado wrote: Before doing so, we'd like to get some feedback about out planned move, so if you have any questions, comments or feedback, please reply to this thread. +1 I think this is the right way to go. I put a lot of work into javelin related stuff a bit

Re: [openstack-dev] [openstack-infra] Using Neutron client in the gate

Hi Gal, One simple way is to get credentials from clouds.yaml (through os-client-config). devstack prepares clouds.yaml (~/.config/openstack/clouds.yaml) which contains both devstack-admin (admin) and devstack (demo) account. neutronclient functional test is a good example.

Re: [openstack-dev] [oslo.messaging] configurable ack-then-process (at least/most once) behavior

Hi, I also left my comment in the patch which explains what we need from Mistral perspective. Please take a look. Renat Akhmerov @ Mirantis Inc. > On 02 Dec 2015, at 17:01, Bogdan Dobrelya wrote: > >> Bogdan, >> >> Which service would use this flag to start with?

Re: [openstack-dev] [oslo.db][sqlalchemy][mistral] Configuring default transaction isolation level

> On 08 Dec 2015, at 21:10, Mike Bayer wrote: > > > > On 12/08/2015 07:28 AM, Renat Akhmerov wrote: >> Hi, >> >> Moshe, thanks a lot for bringing this up. I remember I tried to find a >> way to change isolation level per connection but also was unable to do that. > >

Re: [openstack-dev] [python-novaclient] history of virtual-interface commands

Hi, Also hitting this as making new microversion and would need to have support in CLI. Seems CLI works just by bumping API_MAX_VERSION (as I am only adding one new attribute to existing API). Anyhow cannot do this because microversion 2.12 is not implemented (actually API_MAX_VERSION is

[openstack-dev] [QA][Tempest] Drop javelin off tempest

Hi All, In today's QA meeting we were discussing about dropping Javelin off tempest if it's not being used anymore in grenade, as sdague pointed out. We were thinking about this as a part of the work for [1], where we hit issue on Javelin script testing where gate did not detect the service

Re: [openstack-dev] [ironic] RFC: stop using launchpad milestones and blueprints

On 12/09/2015 10:58 PM, Jim Rollenhagen wrote: On Fri, Dec 04, 2015 at 05:38:43PM +0100, Dmitry Tantsur wrote: Hi! As you all probably know, we've switched to reno for managing release notes. What it also means is that the release team has stopped managing milestones for us. We have to

Re: [openstack-dev] Mitaka Infra Sprint

Hey, Sorry about the formatting on my last email. Clearly my copy+paste skills are lacking. Let me try again in case anybody was confused: Hi all, As discussed during the infra-meeting on Tuesday[0], the infra team will be holding a mid-cycle sprint to focus on infra-cloud[1]. The sprint is

Re: [openstack-dev] [ironic] RFC: stop using launchpad milestones and blueprints

Hi all, fix for tests in #2 is on review, https://review.openstack.org/#/c/255811/ cheers, On Thu, Dec 10, 2015 at 1:15 PM Dmitry Tantsur wrote: > On 12/09/2015 10:58 PM, Jim Rollenhagen wrote: > > On Fri, Dec 04, 2015 at 05:38:43PM +0100, Dmitry Tantsur wrote: > >> Hi! >

Re: [openstack-dev] [Openstack-operators] [openstack-ansible] Mid Cycle Sprint

Great initiative, I'd definitely like to be a part of the mid-cycle. I can't guarantee attendance, but London would be easier for me to do also. For topics, I'd like to see more done about: - streamlining new role creation, or generally making it easier for newer contributors - +1 to Major,

Re: [openstack-dev] [oslo][glance][all] Removing deprecated functions from oslo_utils.timeutils

On Thu, Dec 10, 2015 at 11:10 AM, Flavio Percoco wrote: > On 10/12/15 08:21 -0600, Brant Knudson wrote: > >> >> >> On Thu, Dec 10, 2015 at 7:26 AM, Sean Dague wrote: >> >>On 12/10/2015 01:56 AM, Joshua Harlow wrote: >>> Shouldn't be to hard (although

Re: [openstack-dev] [nova] Contribution to improve Nova's config option space

In case you are one of the people who are already working on patches for this, you might have observed a merge conflict with your patches in the last days. Ed Leafe and I are working on a approach to reduce that. It's basically a list of placeholders in the file "nova/conf/__init__.py" in the

Re: [openstack-dev] [ceilometer][aodh][vitrage] Raising custom alarms in AODH

Hi Ryota, > -Original Message- > From: Ryota Mibu [mailto:r-m...@cq.jp.nec.com] > Sent: Tuesday, December 08, 2015 11:17 AM > > In short, 'event' is generated in OpenStack, 'alarm' is defined by a > user. 'event' is a container of data passed from other OpenStack > services through

Re: [openstack-dev] [oslo][all] The lock files saga (and where we can go from here)

Could the work for the tooz variant be leveraged to add a truly distributed solution (with the proper tooz distributed backend)? IF so, then +1 to this idea. Cinder will be implementing a version of tooz based distribute locks, so having it in Olso someday is a goal I'd think.

Re: [openstack-dev] [trove] Upcoming specs and blueprints for Trove/Mitaka

Amrith/Victoria, Thanks for the heads up about this these blueprints for the Mitaka cycle. This looks like a lot of work but there shouldn’t be a reason to hold back new blueprints this early in the cycle if they plan on being completed in Mitaka. Can we get these blueprints written up and

Re: [openstack-dev] [puppet] Puppet OpenStack Mid-Cycle (Mitaka)

On 11/24/2015 05:41 AM, Emilien Macchi wrote: > Hello, > > If you're involved in Puppet OpenStack or if you want to be involved, > please look at this poll: http://goo.gl/forms/lsBf55Ru8L > > Thanks a lot for your time, So we got 18 people interested by participating to a Puppet midcycle. The

Re: [openstack-dev] [oslo][glance][all] Removing deprecated functions from oslo_utils.timeutils

On 10/12/15 08:21 -0600, Brant Knudson wrote: On Thu, Dec 10, 2015 at 7:26 AM, Sean Dague wrote: On 12/10/2015 01:56 AM, Joshua Harlow wrote: > Shouldn't be to hard (although it's probably not on each oslo project, > but on the consumers projects). > > The

Re: [openstack-dev] [stable] Stable team PTL nominations are open

On 12/9/2015 4:22 AM, Kuvaja, Erno wrote: -Original Message- From: Thierry Carrez [mailto:thie...@openstack.org] Sent: 09 December 2015 08:57 To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [stable] Stable team PTL nominations are open Thierry Carrez wrote: Thierry

Re: [openstack-dev] [Sender Auth Failure] [infra][release][all] Automatic .ics generation for OpenStack's and project's deadlines

I think this is a great idea. +1 —N. > On Dec 10, 2015, at 1:20 PM, Flavio Percoco wrote: > > Greetings, > > I'd like to explore the possibility of having .ics generated - pretty > much the same way we generate it for irc-meetings - for the OpenStack > release schedule and

Re: [openstack-dev] [QA][Tempest] Drop javelin off tempest

Hi All, comments inline El 10/12/15 a las 17:17, Matthew Treinish escribió: > On Thu, Dec 10, 2015 at 11:15:06AM +0100, Daniel Mellado wrote: >> Hi All, >> >> In today's QA meeting we were discussing about dropping Javelin off >> tempest if it's not being used anymore in grenade, as sdague

[openstack-dev] What's Up, Doc? Holiday Edition

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi everyone, This is my final newsletter for the year, as I'm taking summer vacation over the next few weeks (yay for Southern Hemisphere weather!). Your regularly scheduled programming will resume in mid-January. I would like to take a moment

[openstack-dev] [Cinder] Is there anyone truly working on this issue https://bugs.launchpad.net/cinder/+bug/1520102?

Hi Mitsuhiro, Thang The patch https://review.openstack.org/#/c/228916 is merged, but sadly it does not cover the issue https://bugs.launchpad.net/cinder/+bug/1520102. This bug is still valid. As far as you know, is there someone working on this issue? If not, I am gonna fix it. Best wishes,

Re: [openstack-dev] [QA][Tempest] Drop javelin off tempest

Hi, Yes, That's very valid point about there might be some real users or in future. So Instead of deleting it, how about maintaining it. Only issue here was gate did not capture the issues when introduced in his tool. But we can cover that using Unit tests and if really necessary we can add

[openstack-dev] [Tacker] Next IRC weekly meeting in APAC timezone

Tackers, We now have contributors from APAC region, particularly the ones contributing to Enhanced VNF Placement area. As discussed in the last meeting, as a one time change, the next week's IRC meeting will be held in an APAC friendly time slot. When: 0100 UTC Wed Dec 16th (Tue 5PM PST, Wed 9AM

Re: [openstack-dev] Mesos Conductor using container-create operations

Hi Ton, Thanks for the feedback. Here is a clarification. The proposal is neither for using existing DSL to express a container, nor for investing a new DSL. Instead, I proposed to hide the complexity of existing DSLs and expose a simple API to users. For example, if users want to create a

Re: [openstack-dev] [Kuryr] Testing, Rally and Wiki

Great! Would try to offer a hand on the wiki and testing. On Thu, Dec 10, 2015 at 10:11 PM, Gal Sagie wrote: > Hello everyone, > > As some of you have already noticed one of the top priorities for Kuryr > this cycle is to get > our CI and gate testing done. > > I have been

[openstack-dev] [ironic]Unable to locate configuration file in second reboot

Hi, all Something goes wrong when the vm reboot again. The console outputs: "Unable to locate configuration file. Boot failed: press a key to retry, or wait for reset..." And my tftp.conf like this http://paste.openstack.org/show/481472/ I upload a movie in

[openstack-dev] [Kuryr] Testing, Rally and Wiki

Hello everyone, As some of you have already noticed one of the top priorities for Kuryr this cycle is to get our CI and gate testing done. I have been working on creating the base for adding integration tests that will run in the gate in addition to our unit tests and functional testing. If you

[openstack-dev] [oslo][oslo.config][oslo.service] Dynamic Reconfiguration of OpenStack Services

Hi guys, Are there some progress with reloading configuration? Could we restore oslo-config review https://review.openstack.org/#/c/213062/ ? Marian __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [mistral] Improving Mistral pep8 rules files to match Mistral guidelines

Moshe, I will create blueprint for that and will attach link to etherpad, so we can form list of the rules all together. After that it will be possible to publish all our 'rules' to docs and start their implementation. On Thu, Dec 10, 2015 at 11:23 AM, ELISHA, Moshe (Moshe) <

Re: [openstack-dev] [oslo][glance][all] Removing deprecated functions from oslo_utils.timeutils

On 12/10/2015 01:56 AM, Joshua Harlow wrote: > Shouldn't be to hard (although it's probably not on each oslo project, > but on the consumers projects). > > The warnings module can turn warnings into raised exceptions with a > simple command line switch btw... > > For example: > > $ python

[openstack-dev] [Fuel] Christmas Core Cleanup

Hey folks, In an effort to do some housekeeping, I clean up the list of core reviewers in Fuel. According to Stackalytics the following cores show a low contribution rate: # fuel-web [1] * Dmitry Shulyak * Evgeniy L # python-fuelclient [2] * Dmitry Pyzhov * Evgeniy L #

[openstack-dev] [glance][all] glance_store drivers deprecation/stabilization: Volunteers needed

Greetings, As some of you know, there's a proposal (still a rough draft) for refactoring the glance_store API. This library is the home for the store drivers used by Glance to save or access the image data. As other drivers in OpenStack, this library is facing the issue of having unmaintained,

Re: [openstack-dev] [ironic]Unable to locate configuration file in second reboot

Hi, On Thu, Dec 10, 2015 at 4:34 AM, Zhi Chang wrote: > > And my tftp.conf like this http://paste.openstack.org/show/481472/ > > I upload a movie in https://youtu.be/jktPIjEmMV8, at 04:30 there is a > error happens. > > Could someone give me some idea?

Re: [openstack-dev] [Tacker][Tricircle]Multi-VIM collaboration

Hi, Sridhar, Great to know that Tacker also begins to address multi-VIM ( multi-OpenStack ) requirement in OPNFV cloud, and your concerns on OPNFV multisite and OpenStack Tricircle project. I just gave some comment on the spec. And I think the most important one for Tacker integration with

Re: [openstack-dev] [ironic]Unable to locate configuration file insecond reboot

hi, thanks for your reply. Another DHCP server reply this machine. Now, I have already stop that DHCP server. But there is another problem, let me describe it. When I use "nova boot" command to boot a machine. Nova-conductor always says "error", The detail info is "NoValidHost: No valid

[openstack-dev] [keystone] removing keystoneclient.middleware (in favor of keystonemiddleware)

keystonemiddleware has been around since July 2014 [0], it was forked from keystoneclient.middleware which we deprecated around the same time [1] (Juno time frame). A few cycles later... is anyone still clinging onto keystoneclient.middleware? Or can we remove it and cut a new major version of

[openstack-dev] [midonet] Request For Enhancement(RFE) process

Hi All, For feature proposal in MidoNet, I would like that we follow the RFE process[1] currently practiced in Neutron. It is designed to be lightweight which makes it easy for everyone, including non-developers, to initiate the feature development process. I believe this process is appropriate

Re: [openstack-dev] [Fuel] Christmas Core Cleanup

Hi, Thank you Igor for cleaning core related groups. Also I would like to add that many of removed cores are still SME (subject matter experts) in specific areas, so they will continue reviewing related patches. Thanks, On Thu, Dec 10, 2015 at 2:42 PM, Igor Kalnitsky

Re: [openstack-dev] [Kuryr] Testing, Rally and Wiki

Hi Gal, Would be happy to help. Please count me IN. -Vikas Choudhary On Thu, Dec 10, 2015 at 7:41 PM, Gal Sagie wrote: > Hello everyone, > > As some of you have already noticed one of the top priorities for Kuryr > this cycle is to get > our CI and gate testing done. >

Re: [openstack-dev] [neutron][tap-as-a-service] Tap-as-a-service API

Excellent. I will take a look. Thanks for taking care of this! Fawad Khaliq On Fri, Dec 11, 2015 at 10:18 AM, Takashi Yamamoto wrote: > On Fri, Dec 4, 2015 at 2:38 AM, Fawad Khaliq wrote: > > Thanks Yamamoto. Yes, agree it makes sense to keep it in

[openstack-dev] [Fuel] Moved blueprints out of 8.0

Hi all, I've moved the following blueprints: https://etherpad.openstack.org/p/fuel-moved-bps-from-8.0 I called for blueprints status update at [1], [2], [3], [4], and suggested to move those which are not "Implemented". Now I finally did, except test/doc related (which can be done after FF). I

Re: [openstack-dev] [Cinder] Is there anyone truly working on this issue https://bugs.launchpad.net/cinder/+bug/1520102?

I have to try it again myself. What errors are you seeing? Is it the same? Feel free to post a patch if you already have one that would solve it. Regards, Thang On Thu, Dec 10, 2015 at 10:51 PM, Sheng Bo Hou wrote: > Hi Mitsuhiro, Thang > > The patch

Re: [openstack-dev] [neutron][tap-as-a-service] Tap-as-a-service API

On Fri, Dec 4, 2015 at 2:38 AM, Fawad Khaliq wrote: > Thanks Yamamoto. Yes, agree it makes sense to keep it in the TaaS tree. > Would be great though to have broader audience come and review it. > > Seems like there is not much activity. I can go ahead and take a stab at >

Re: [openstack-dev] [Kuryr] Testing, Rally and Wiki

Hi Boris, The way i envision it, is for this to first implement Docker resources (networks, containers) which are deployed in a mixed OpenStack environments and use Kuryr to plug their network. Then we can create some scenarios to benchmark and test these mixed environments with Kuryr or with

Re: [openstack-dev] [Fuel] Christmas Core Cleanup

Igor, thank you for driving this. I think that this is a great practice: we need to keep list of cores up to date. What about other repos, not mentioned here? Are those are fine being as is? What about fuel-docs, for instance? For instance, I see that Irina was able to provide just 5 reviews

[openstack-dev] [nova][serial-console-proxy]

Hi All, I have set up open stack on an Arm64 machine and all the open stack related services are running fine. Also am able to launch an instance successfully. Now that I need to get a console for my instance. The noVNC console is not supported in the machine am using. So I have to use a

Re: [openstack-dev] [oslo][glance][all] Removing deprecated functions from oslo_utils.timeutils

Brant, That's a great pattern for everyone to follow. Thanks! Dims On Thu, Dec 10, 2015 at 5:21 PM, Brant Knudson wrote: > > > On Thu, Dec 10, 2015 at 7:26 AM, Sean Dague wrote: >> >> On 12/10/2015 01:56 AM, Joshua Harlow wrote: >> > Shouldn't be to hard

Re: [openstack-dev] [nova] Testing concerns around boot from UEFI spec

On 12/10/2015 2:21 AM, Ren, Qiaowei wrote: -Original Message- From: Sean Dague [mailto:s...@dague.net] Sent: Friday, December 4, 2015 9:47 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [nova] Testing concerns around boot from UEFI spec On 12/04/2015 08:34 AM,

Re: [openstack-dev] [nova][cinder] what are the key errors with volume detach

On 12/02/2015 12:37 PM, Rosa, Andrea (HP Cloud Services) wrote: > Hi > > thanks Sean for bringing this point, I have been working on the change and on > the (abandoned) spec. > I'll try here to summarize all the discussions we had and what we decided. > >> From: Sean Dague

[openstack-dev] Reg: Blueprint -- add-compute-node-on-the-go

Hi, I have added the blue print https://blueprints.launchpad.net/nova/+spec/add-compute-node-on-the-go. Can you please let me know the feasibility, and accept the blueprint. Thanks & Regards,  Atul Agarwal Tata Consultancy Services Mailto: atul...@tcs.com Website: http://www.tcs.com

Re: [openstack-dev] [oslo][glance][all] Removing deprecated functions from oslo_utils.timeutils

On Thu, Dec 10, 2015 at 7:26 AM, Sean Dague wrote: > On 12/10/2015 01:56 AM, Joshua Harlow wrote: > > Shouldn't be to hard (although it's probably not on each oslo project, > > but on the consumers projects). > > > > The warnings module can turn warnings into raised exceptions

Re: [openstack-dev] [nova][cinder] what are the key errors with volume detach

On 12/2/2015 11:37 AM, Rosa, Andrea (HP Cloud Services) wrote: Hi thanks Sean for bringing this point, I have been working on the change and on the (abandoned) spec. I'll try here to summarize all the discussions we had and what we decided. From: Sean Dague [mailto:s...@dague.net] Sent: 02

Re: [openstack-dev] [Openstack-operators] [openstack-ansible] Mid Cycle Sprint

Count me in as wanting to be part of the mid-cycle. I live in San Antonio but I think we should strongly consider having the meetup in the UK. It seems most of our deployers live in the UK and it'd be nice to get people involved whom may not have been able to attend the summit. While I'll need

Re: [openstack-dev] [packaging] liberty doesn't have caps on deps

On 10/16/2015 7:16 AM, Sean Dague wrote: On 10/16/2015 04:23 AM, Thierry Carrez wrote: Robert Collins wrote: [...] BUT: we haven't (ever!) tested that the lowest versions we specify work. When folk know they are adding a hard dependency on a version we do raise the lower versions, but thats

[openstack-dev] [vitrage] Last vitrage meeting

Hi, Our last Vitrage meeting was not recorded properly due to an update of OpenStack bot that was performed in the middle of our meeting. Anyway, you can still view the meeting log in http://eavesdrop.openstack.org/meetings/vitrage/2015/vitrage.2015-12-09-09.00.log.txt Ifat.

[openstack-dev] [trove] Upcoming specs and blueprints for Trove/Mitaka

Members of the Trove community, Over the past couple of weeks we have discussed the possibility of an early deadline for submission of trove specifications for projects that are to be included in the Mitaka release. I understand why we're doing it, and agree with the concept. Unfortunately

Re: [openstack-dev] [Fuel] Christmas Core Cleanup

Hi Evgeniy, Yes, you absolutely right! I as far as possible will ask them to review certain patches (if they have no time to watch all patches_. Moreover, I'm going to add them to MAINTAINERS file. Thanks, Igor P.S: I hope you and others will manage to spend more time on Fuel, since your

Re: [openstack-dev] [QA][Tempest] Drop javelin off tempest

On Thu, Dec 10, 2015 at 11:15:06AM +0100, Daniel Mellado wrote: > Hi All, > > In today's QA meeting we were discussing about dropping Javelin off > tempest if it's not being used anymore in grenade, as sdague pointed > out. We were thinking about this as a part of the work for [1], where we > hit

Re: [openstack-dev] [Fuel] Configuration management for Fuel 7.0

Hi there, one small step into this direction. I've checked how idempotent controller's tasks. As result bugs below were reported: https://bugs.launchpad.net/fuel/+bug/1524759 NEW https://bugs.launchpad.net/fuel/+bug/1524747 NEW https://bugs.launchpad.net/fuel/+bug/1524731 NEW