[openstack-dev] [Horizon] Weekly wrap-up

Hi folks, We're well on our way to RC2, which will probably be tagged early next week unless someone objects.We've got the requirements.txt updates for the xstatic packages in but just need those last couple of domain context related patches to get in (poke, poke...) Use domain_context not

[openstack-dev] [telemetry] Pollsters for Veritas HyperScale

Hi Everyone, Find below details of Ceilometer pollsters for Veritas HyperScale. Please suggest how we can take this forward for merge. Regards, Nirendra -- Overview: * HyperScale pollsters are required to collect and monitor HyperScale storage statistics. * Collected statistics can be

[openstack-dev] [gate][neutron][infra] tempest jobs timing out due to general sluggishness of the node?

Hi all, I noticed lately a number of job failures in neutron gate that all result in job timeouts. I describe gate-tempest-dsvm-neutron-dvr-ubuntu-xenial job below, though I see timeouts happening in other jobs too. The failure mode is all operations, ./stack.sh and each tempest test take

Re: [openstack-dev] Mitaka - Unable to attach volume to VM

On Thu, Feb 9, 2017 at 9:04 PM, Sam Huracan wrote: > Hi Sean, > > I've checked 'openstack volume list', the state of all volume is avaiable, > and I can download image to volume. > I also use Ceph as other Cinder volume backend, and issue is similarly. > Same log. > >

Re: [openstack-dev] Mitaka - Unable to attach volume to VM

Hi Sean, I've checked 'openstack volume list', the state of all volume is avaiable, and I can download image to volume. I also use Ceph as other Cinder volume backend, and issue is similarly. Same log. Port 3260 have opened on iptables. When I nova --debug volume-attach, I see nova contact to

Re: [openstack-dev] [All] IRC Mishaps

... because I'm lazy and haven't brought my bouncer back online: j #openstack-meeting-alt Yes, I like to remind 'j' often that there is a channel called openstack-meeting-alt instead of actually joining it myself. > On Feb 9, 2017, at 10:14 PM, Sean McGinnis wrote: >

Re: [openstack-dev] [kolla] Domains support

OK great !!! Now, I have a working LDAP setup! Thanks for your help. Now, about the modifications done to Horizon's config file (in fact, in local_settings), I had to perform these changes through the local_settings.j2 template file. Is this the place where modifications go or is there any

[openstack-dev] [daisycloud-core] Agenda for IRC meeting 0800UTC Feb. 10 2017

1) Roll Call 2) OPNFV: Release Postpone Discuss 3) OPNFV: BM/BM Deployment & Functest Integration 4) OpenStack: Core Code Definition Wind Up B. R., Zhijiang__ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] Mitaka - Unable to attach volume to VM

On Fri, Feb 10, 2017 at 02:18:15AM +0700, Sam Huracan wrote: > Hi guys, > > I meet this issue when deploying Mitaka. > When I attach LVM volume to VM, it keeps state "Attaching". I am also > unable to boot VM from volume. > > This is /var/log/nova/nova-compute.log in Compute node when I attach

Re: [openstack-dev] [All] IRC Mishaps

On Thu, Feb 09, 2017 at 08:43:05PM +, Chandrasekar, Dharini wrote: > My IRC mishaps go like: > > Tried to set a channel topic and ended up making it > look like messages sent on the channel instead. > Oh, there was the time I accidentally banned everyone from the Cinder channel. That was

[openstack-dev] [monasca] Ideas to work on

Hi Anqi, You had expressed a strong interest in working on Monasca the other day in our Weekly Monasca Team Meeting. I owed you a response. The team had also asked me to also keep them in the loop. Here is a list that I feel is interesting, that is not trivial or extremely complex (just right

Re: [openstack-dev] [release] Support phase clarification

> > Yup I think 6 months makes sense. I'll work up a change to the releases repo > to record the target date for switching between Phases and EOL dates. > > There will be a little duplication of data but I think we can live with that. > > Yours Tony. Perfect - thanks Tony and Jeremy! Exactly

Re: [openstack-dev] [designate] Status of the project

On 02/09/2017 02:19 PM, Hayes, Graham wrote: Where too now then? === Well, this is where I call out to people who actually use the project - don't jump ship and use something else because of the picture I have painted. We are a dedicated team, how cares about the project. We

Re: [openstack-dev] [release] Support phase clarification

On 2/7/2017 11:52 AM, Jay S Bryant wrote: This would also mean we would need to be careful to ensure that any backports to Newton also make it into Ocata to avoid holes in fix coverage.> You have to do this regardless. Just saying. -- Thanks, Matt Riedemann

Re: [openstack-dev] [release][oslo] recreating the stable/ocata branch for mox3

agree, that's a decent way 2017-02-09 21:24 GMT+08:00 Doug Hellmann : > Excerpts from ChangBo Guo's message of 2017-02-09 15:21:55 +0800: > > I just added it in https://etherpad.openstack.org/p/community-goals > > yesterday. submit a community goal for this ? > > Someone

Re: [openstack-dev] [release] Support phase clarification

On Thu, Feb 09, 2017 at 06:26:57PM -0600, Jay S Bryant wrote: > > > On 2/9/2017 6:09 PM, Sean McGinnis wrote: > > On Thu, Feb 09, 2017 at 05:41:26PM +, Jeremy Stanley wrote: > > > On 2017-02-09 11:24:46 -0600 (-0600), Sean McGinnis wrote: > > > [...] > > > > Thanks both. The original

Re: [openstack-dev] [tripleo][kolla][openstack-helm][kuryr] OpenStack on containers leaveraging kuryr

On Thu, Feb 9, 2017 at 10:00 PM, Dan Sneddon wrote: > Pete, thanks for mentioning network isolation and segmentation. That's > my area of interest, since I'm focused on underlay networking for > TripleO and bare-metal networking in Ironic. > > Network isolation is going to

Re: [openstack-dev] [release] Support phase clarification

On 2/9/2017 6:09 PM, Sean McGinnis wrote: On Thu, Feb 09, 2017 at 05:41:26PM +, Jeremy Stanley wrote: On 2017-02-09 11:24:46 -0600 (-0600), Sean McGinnis wrote: [...] Thanks both. The original question still stands though. Are we rolling over support phases at the 6 month boundary as

Re: [openstack-dev] [release] Support phase clarification

On 2017-02-09 18:09:39 -0600 (-0600), Sean McGinnis wrote: [...] > Thanks Jeremy. Something must be getting lost in translation with my question > though. :) > > I am just going to assume that the support phases are in fact 6 months, so > Newton will still be a fully active stable branch for a

Re: [openstack-dev] [neutron][taas] ocata

done. vinay or anil, can you update launchpad? i don't have permission. On Wed, Feb 8, 2017 at 3:36 PM, Soichi Shigeta wrote: > > Hi Yamamoto, > >We discussed this on today's IRC and agreed to make an ocata release. > >Best regards, >Soichi > > > >>

Re: [openstack-dev] [release] Support phase clarification

On Thu, Feb 09, 2017 at 05:41:26PM +, Jeremy Stanley wrote: > On 2017-02-09 11:24:46 -0600 (-0600), Sean McGinnis wrote: > [...] > > Thanks both. The original question still stands though. Are we rolling > > over support phases at the 6 month boundary as stated, or is the intent > > actually

Re: [openstack-dev] [nova] Next minimum libvirt version

On 02/09/2017 05:51 PM, Steve Gordon wrote: > - Original Message - >> From: "Matt Riedemann" >> To: "OpenStack Development Mailing List (not for usage questions)" >> , >> openstack-operat...@lists.openstack.org >> Sent: Thursday,

Re: [openstack-dev] [nova] Next minimum libvirt version

- Original Message - > From: "Matt Riedemann" > To: "OpenStack Development Mailing List (not for usage questions)" > , > openstack-operat...@lists.openstack.org > Sent: Thursday, February 9, 2017 6:29:22 PM > Subject:

[openstack-dev] [nova] Next minimum libvirt version

Since danpb hasn't been around I've sort of forgotten about this, but we should talk about bumping the minimum required libvirt version in nova. Currently it's 1.2.1 and the next was set to 1.2.9. On master we're gating on ubuntu 14.04 which has libvirt 1.3.1 (14.04 had 1.2.2). If we move

Re: [openstack-dev] [All] IRC Mishaps

On 02/09/2017 10:43 AM, Clint Byrum wrote: > Excerpts from Mark Voelker's message of 2017-02-09 15:41:33 +: >> I work with lots of different clouds and any time I switch focus to a >> terminal I have to figure out which cloud it’s environment is set up to use. >> My terminal emulator has

Re: [openstack-dev] [All] IRC Mishaps

The fact that I'm prone to off-by-one errors (particularly when typing spaces) has reconditioned me to no longer use "got it" in chat conversation. On Thu, Feb 9, 2017 at 3:37 PM, Matt Riedemann wrote: > On 2/9/2017 9:47 AM, Hayes, Graham wrote: > >> >> I have also had some

Re: [openstack-dev] [All] IRC Mishaps

On 2/9/2017 9:47 AM, Hayes, Graham wrote: I have also had some ... unfortunate ... typos over the years. Changing one letter of some words can really give a message a completely different meaning :) Also, I have '/j #openstack-meeting' and then '#startmeeting' while on a completely different

Re: [openstack-dev] [tripleo][kolla][openstack-helm][kuryr] OpenStack on containers leaveraging kuryr

Pete, thanks for mentioning network isolation and segmentation. That's my area of interest, since I'm focused on underlay networking for TripleO and bare-metal networking in Ironic. Network isolation is going to be important for several reasons: 1) Separation of control and data plane in

Re: [openstack-dev] [All] IRC Mishaps

My IRC mishaps go like: Tried to set a channel topic and ended up making it look like messages sent on the channel instead. Another moment was when I accidentally sent a PM to a channel. (wrong window moment) Dharini irc: dharinic. > >On 2/8/17, 5:04 PM, "Jay Pipes"

[openstack-dev] [charms]

Hello Charmers, Today marks the start of regular feature freeze of OpenStack Charms, for the planned OpenStack Charms stable release on Feb 23. During this time, we focus on any critical bug fixes, any items with a feature freeze exception, additional test coverage, and an increase in edge case

Re: [openstack-dev] [All] IRC Mishaps

One of my embarrassing moments ... Sent a partial message accidentally in IRC meeting by hitting “Enter” instead of “Backspace” ☹ Anindita Das irc: dasanind On 2/8/17, 5:04 PM, "Jay Pipes" wrote: On 02/08/2017 03:36 PM, Kendall Nelson wrote: > Hello All! >

[openstack-dev] [designate] Status of the project

The HTML version of this is here: http://graham.hayes.ie/posts/openstack-designate-where-we-are/ I have been asked a few times recently "What is the state of the Designate project?", "How is Designate getting on?", and by people who know what is happening "What are you going to do about

[openstack-dev] Mitaka - Unable to attach volume to VM

Hi guys, I meet this issue when deploying Mitaka. When I attach LVM volume to VM, it keeps state "Attaching". I am also unable to boot VM from volume. This is /var/log/nova/nova-compute.log in Compute node when I attach volume. http://paste.openstack.org/show/598282/ Mitaka version:

[openstack-dev] [release] Release countdown for week R-1, 13-17 Feb

Focus - We are in the release candidate phase of the cycle. All project teams should be fixing last minute release-critical bugs and testing the prepared release candidates for their deliverables. Release Tasks - Please land translation patches as quickly as possible so we can

[openstack-dev] [all] PTG: extra reservable Discussion rooms (with projection)

Hi everyone, As mentioned in [1], we'll have a number of extra reservable rooms at the PTG in Atlanta. The plan is for teams to book those extra rooms when they need a larger fishbowl setting (for example large inter-project discussions) or access to videoprojection to share the same screen (most

Re: [openstack-dev] [tripleo][kolla][openstack-helm][kuryr] OpenStack on containers leaveraging kuryr

Michal, It's actually really easy to achieve in k8s, provided we make some concessions: at least one keystone and neutron API pod needs to run in the host's network namespace (and the supporting DB's). This may not be acceptable for Tripple-O, but I'm pretty sure we could find a workable solution

Re: [openstack-dev] [release][all] HELP NEEDED: test failures blocking requirements ocata branch and opening of pike

On 9 February 2017 at 05:16, Doug Hellmann wrote: > Excerpts from Doug Hellmann's message of 2017-02-08 23:54:06 -0500: > > The patch to update the XStatic package versions [1] is blocked by a > > patch to remove nova-docker from the requirements project sync list [2], > >

Re: [openstack-dev] [kuryr] Resource management videoconf meeting

On Thu, Feb 9, 2017 at 7:48 AM, Antoni Segura Puimedon wrote: > > > On Tue, Feb 7, 2017 at 5:30 PM, Antoni Segura Puimedon > wrote: > >> Hi all, >> >> In the last weekly IRC meeting it was agreed to hold a videoconf meeting >> about resource management.

Re: [openstack-dev] [tripleo][kolla][openstack-helm][kuryr] OpenStack on containers leaveraging kuryr

So from kolla (and kolla-k8s) point of view, this is chicken egg problem:) We could use kuryr for our networking, but who will deploy kuryr? We don't have undercloud concept in any of kollas so far. With Kolla-ansible we really use host networking all the way and for k8s we have k8s networking

Re: [openstack-dev] [tripleo][kolla][openstack-helm][kuryr] OpenStack on containers leaveraging kuryr

Hi Flavio, I've been doing some work on packaging Kuryr for use with K8s as an underlay for OpenStack on Kubernetes. When we met up in Brno the Harbor project I showed you used Tony's old Raven Prototype to provide the network isolation and segmentation in K8s. I've since begun to lay the

Re: [openstack-dev] [release] Support phase clarification

On 2017-02-09 11:24:46 -0600 (-0600), Sean McGinnis wrote: [...] > Thanks both. The original question still stands though. Are we rolling > over support phases at the 6 month boundary as stated, or is the intent > actually to be on the release boundaries? Note this was also discussed here a

Re: [openstack-dev] [release][all] HELP NEEDED: test failures blocking requirements ocata branch and opening of pike

On Thu, Feb 9, 2017 at 2:16 PM, Doug Hellmann wrote: > Excerpts from Doug Hellmann's message of 2017-02-08 23:54:06 -0500: >> The patch to update the XStatic package versions [1] is blocked by a >> patch to remove nova-docker from the requirements project sync list [2], >>

Re: [openstack-dev] [release] Support phase clarification

On Thu, Feb 09, 2017 at 05:10:00PM +0800, ChangBo Guo wrote: > Just copy statement from > http://docs.openstack.org/project-team-guide/stable-branches.html#support-phases > > "*The exact length of any given stable branch life support is discussed > amongst stable branch maintainers and

[openstack-dev] [all][api] POST /api-wg/news

Greetings OpenStack community, This week's meeting[0] was relatively light, with some discussion about the recently released Ethercalc[4], and the first draft of the API compatiblity guideline[5] (many thanks to Chris Dent). The compatibility guideline lays out some concrete standards by

Re: [openstack-dev] [All] IRC Mishaps

Excerpts from Mark Voelker's message of 2017-02-09 15:41:33 +: > I work with lots of different clouds and any time I switch focus to a > terminal I have to figure out which cloud it’s environment is set up to use. > My terminal emulator has the same color scheme as my IRC client, so I’ve >

Re: [openstack-dev] [All] IRC Mishaps

On one occasion I was sharing links in a meeting, and kept typing #url , until someone was gracious enough to ask me in a private conversation what was the meaning of #url. On another occasion, I was substituting for the meeting chair person and typed #startmeeting wrong-meeting-name. When the

Re: [openstack-dev] [tripleo][kolla][openstack-helm][kuryr] OpenStack on containers leaveraging kuryr

Flavio, This is a great opportunity, and we would very much like to contribute. In fact, there are developers that span both Kolla-Kubernetes and Openstack-Helm and I am sure they would be perfect resources for what you’re looking for. What is a good “next step” for getting involved? I believe

Re: [openstack-dev] [All] IRC Mishaps

On 9 February 2017 at 07:43, Morales, Victor wrote: > One of my favorites is the usage of #undo command during the meetings for > fixing a quick copy & paste link. Should be necessary to include more > information in this wiki entry[1] > Yes, I can't count the number

Re: [openstack-dev] [TripleO] Proposing Dmitry Tantsur and Alex Schultz as instack-undercloud cores

On 02/09/2017 04:50 PM, Emilien Macchi wrote: Dmitry: you are now allowed to +2 on instack-undercloud & tripleo-docs. Thanks all for your trust! :) Alex: you're now allowed to +2 on instack-undercloud. Thanks folks, keep rocking! On Wed, Feb 1, 2017 at 8:05 AM, Jiří Stránský

Re: [openstack-dev] [TripleO] Proposing Dmitry Tantsur and Alex Schultz as instack-undercloud cores

Dmitry: you are now allowed to +2 on instack-undercloud & tripleo-docs. Alex: you're now allowed to +2 on instack-undercloud. Thanks folks, keep rocking! On Wed, Feb 1, 2017 at 8:05 AM, Jiří Stránský wrote: > On 31.1.2017 19:08, Ben Nemec wrote: >> >> >> >> On 01/31/2017 11:03

Re: [openstack-dev] [tripleo] Moving mirror server images to tarballs.o.o (Was: [rdo-list] RDO-CI Scrum Weekly Scrum Recap)

On 02/08/2017 01:28 PM, Jeremy Stanley wrote: On 2017-02-08 14:10:16 -0500 (-0500), Paul Belanger wrote: [...] We basically create a publisher in JJB to handle this, which looks in the $WORKSPACE/images folder for things to scp to tarballs.o.o. Take a look at the kolla job for example. What

Re: [openstack-dev] [tripleo][kolla][openstack-helm][kuryr] OpenStack on containers leaveraging kuryr

Flavio, I think Michal (inc0) was planning to reach out to the TripleO team to at least get one or more design sessions in Wednesday. Kolla’s PTG schedule for Monday and Tuesday is packed with a wait list of topics. I depart IIRC Wednesday at 11AM – I had asked inc0 if we do these we do them

Re: [openstack-dev] [All] IRC Mishaps

On 09/02/2017 14:42, Jim Rollenhagen wrote: > On Thu, Feb 9, 2017 at 8:38 AM, Hayes, Graham > wrote: > > On 08/02/2017 20:39, Kendall Nelson wrote: > > Hello All! > > > > So I am sure we've all seen it: people writing terminal

Re: [openstack-dev] [All] IRC Mishaps

On 09/02/2017 13:41, Hayes, Graham wrote: > On 08/02/2017 20:39, Kendall Nelson wrote: >> Hello All! >> >> So I am sure we've all seen it: people writing terminal commands into >> our project channels, misusing '/' commands, etc. But have any of you >> actually done it? >> >> If any of you cores,

Re: [openstack-dev] [All] IRC Mishaps

One of my favorites is the usage of #undo command during the meetings for fixing a quick copy & paste link. Should be necessary to include more information in this wiki entry[1] Victor Morales irc: electrocucaracha [1] https://wiki.openstack.org/wiki/UsingIRC From: Rob C

Re: [openstack-dev] [All] IRC Mishaps

I work with lots of different clouds and any time I switch focus to a terminal I have to figure out which cloud it’s environment is set up to use. My terminal emulator has the same color scheme as my IRC client, so I’ve probably typed “set | grep OS_” into IRC accidentally about a million

Re: [openstack-dev] [All] IRC Mishaps

Hi, This: http://eavesdrop.openstack.org/meetings/keystone/2017/keystone.2017-01-24-18.01.log.html#l-304 On 02/08/2017 11:36 PM, Kendall Nelson wrote: > Hello All! > > So I am sure we've all seen it: people writing terminal commands into our > project channels, misusing '/' commands, etc. But

Re: [openstack-dev] [All] IRC Mishaps

On 2017-02-09 10:10:28 +1100 (+1100), Michael Still wrote: > At a previous employer we had a policy that all passwords started > with "/" because of the sheer number of times someone typed the > root password into a public IRC channel. [...] I can't even keep count of the number of times I and

Re: [openstack-dev] [All] IRC Mishaps

On 2017-02-08 20:36:16 + (+), Kendall Nelson wrote: > So I am sure we've all seen it: people writing terminal commands > into our project channels [...] Even though I've been a constant IRC user for nearly 3 decades, I still do that with great frequency. It's also amusing to respond to

Re: [openstack-dev] [All] IRC Mishaps

On 2017-02-09 08:26:09 -0500 (-0500), Jim Rollenhagen wrote: > Yubikey users tend to dump randomness in IRC at times, e.g.: > > ccduggvhtnbdlhnnggbudfciuvjvgbdininggijb And the various other keyboard-emulating OTP fobs which regularly spit up some 6-digit series when its user accidentally

Re: [openstack-dev] Glance rolling upgrades database strategy implementation

Dmitry, thanks for your interest and appreciate your enthusiasm to work on it. We've a few folks who are actively contributing to the same and were able to release significant work, though experimental, in Ocata. Please join the team on #openstack-glance or show up at one of our meetings, reach

[openstack-dev] [ironic] PTG planning: please submit your topics by Friday

Hi folks! We have a bit more than a week left till the PTG, and we need to decide on the list of topics to discuss. Big thanks to everyone who already proposed their topics. Those who didn't - please do it by tomorrow, Feb 9. Add your topics to the very bottom of the etherpad:

Re: [openstack-dev] [All] IRC Mishaps

On 2017-02-09 11:14:09 +1000 (+1000), Lana Brindley wrote: [...] > What about the one where you're conducting a private conversation > in one window, and watching a group chat in another one, and then > drop some deeply personal (or embarrassing!) content in the group > chat instead the PM ;) I

[openstack-dev] Glance rolling upgrades database strategy implementation

Hi, I'm going to work on implementation of https://specs.openstack.org/openstack/glance-specs/specs/ocata/approved/glance/database-strategy-for-rolling-upgrades.html . If someone going to also work on this, have any concerns with my role in implementing this blueprint or gonna help me with it,

Re: [openstack-dev] [All] IRC Mishaps

On Thu, Feb 9, 2017 at 8:38 AM, Hayes, Graham wrote: > On 08/02/2017 20:39, Kendall Nelson wrote: > > Hello All! > > > > So I am sure we've all seen it: people writing terminal commands into > > our project channels, misusing '/' commands, etc. But have any of you > >

Re: [openstack-dev] [ironic][qa][grenade] Release blocked on grenade job not testing from newton

On Thu, Feb 9, 2017 at 7:00 AM, Jim Rollenhagen wrote: > Hey folks, > > Ironic plans to release Ocata this week, once we have a couple small > patches > and a release note cleanup landed. > > However, our grenade job is now testing master->master, best I can tell. > This

Re: [openstack-dev] [All] IRC Mishaps

On 08/02/2017 20:39, Kendall Nelson wrote: > Hello All! > > So I am sure we've all seen it: people writing terminal commands into > our project channels, misusing '/' commands, etc. But have any of you > actually done it? > > If any of you cores, ptls or other upstanding members of our wonderful >

Re: [openstack-dev] [ironic][qa][grenade] Release blocked on grenade job not testing from newton

On 02/09/2017 08:22 AM, Jim Rollenhagen wrote: > On Thu, Feb 9, 2017 at 7:51 AM, Sean Dague > wrote: > > On 02/09/2017 07:00 AM, Jim Rollenhagen wrote: > > Hey folks, > > > > Ironic plans to release Ocata this week, once we have a couple >

Re: [openstack-dev] [karbor][stackalytics] Karbor Missing Commits in Stackalytics

Sure, I'll take a look at this. --Ilya 2017-02-09 13:47 GMT+04:00 Zhenguo Niu : > After the rename of Nimble to Mogan, all git-related stats are lost as > well. > > http://stackalytics.com/?metric=commits_type=opensta > ck-others=mogan > > Ilya, Can you please assist with

Re: [openstack-dev] [All] IRC Mishaps

On 09/02/17 08:26 -0500, Jim Rollenhagen wrote: Yubikey users tend to dump randomness in IRC at times, e.g.: ccduggvhtnbdlhnnggbudfciuvjvgbdininggijb Yes! Like all the time because there's no USB port that will be perfect for a yubikey... not even in the back of the laptop. Flavio

Re: [openstack-dev] [All] IRC Mishaps

Yubikey users tend to dump randomness in IRC at times, e.g.: ccduggvhtnbdlhnnggbudfciuvjvgbdininggijb // jim On Wed, Feb 8, 2017 at 3:36 PM, Kendall Nelson wrote: > Hello All! > > So I am sure we've all seen it: people writing terminal commands into our > project

Re: [openstack-dev] [release][oslo] recreating the stable/ocata branch for mox3

Excerpts from ChangBo Guo's message of 2017-02-09 15:21:55 +0800: > I just added it in https://etherpad.openstack.org/p/community-goals > yesterday. submit a community goal for this ? Someone needs to start documenting the sort of work needed (how many projects use mox3, and how much) and putting

Re: [openstack-dev] [ironic][qa][grenade] Release blocked on grenade job not testing from newton

On Thu, Feb 9, 2017 at 7:51 AM, Sean Dague wrote: > On 02/09/2017 07:00 AM, Jim Rollenhagen wrote: > > Hey folks, > > > > Ironic plans to release Ocata this week, once we have a couple small > patches > > and a release note cleanup landed. > > > > However, our grenade job is now

Re: [openstack-dev] [ironic][qa][grenade] Release blocked on grenade job not testing from newton

Excerpts from Sean Dague's message of 2017-02-09 07:51:41 -0500: > On 02/09/2017 07:00 AM, Jim Rollenhagen wrote: > > Hey folks, > > > > Ironic plans to release Ocata this week, once we have a couple small patches > > and a release note cleanup landed. > > > > However, our grenade job is now

Re: [openstack-dev] [release][all] HELP NEEDED: test failures blocking requirements ocata branch and opening of pike

Excerpts from Doug Hellmann's message of 2017-02-08 23:54:06 -0500: > The patch to update the XStatic package versions [1] is blocked by a > patch to remove nova-docker from the requirements project sync list [2], > which is in turn running into issues in the >

Re: [openstack-dev] [All] IRC Mishaps

#startmeeting in the wrong channel #startmeeting in the right channel but at the wrong time #startmeeting in the right channel and at the right time but someone else already started it I'm basically a pro at meetings. On Thu, Feb 9, 2017 at 1:14 AM, Lana Brindley

Re: [openstack-dev] [ironic][qa][grenade] Release blocked on grenade job not testing from newton

On 02/09/2017 07:00 AM, Jim Rollenhagen wrote: > Hey folks, > > Ironic plans to release Ocata this week, once we have a couple small patches > and a release note cleanup landed. > > However, our grenade job is now testing master->master, best I can tell. > This > is pretty clearly due to this

Re: [openstack-dev] [Dragonflow] Nominating Xiao Hong Hui for core of Dragonflow

+1 On Thu, Feb 9, 2017 at 12:16 PM, Omer Anson wrote: > Hello, > > I would like to nominate Xiao Hong Hui as a core reviewer for Dragonflow. > > Since he has joined, Xiao has helped move the project forwards with > important commits and very helpful reviews. He has shown

[openstack-dev] [ironic][qa][grenade] Release blocked on grenade job not testing from newton

Hey folks, Ironic plans to release Ocata this week, once we have a couple small patches and a release note cleanup landed. However, our grenade job is now testing master->master, best I can tell. This is pretty clearly due to this d-s-g commit:

[openstack-dev] [nova] Live migration with claim

Hi, I started to review patch series [1] which addresses the issue with live migration resources. While doing that I made some notes possibly can be useful for reviewers. I would like to share those notes and to ask community to look critically and check if I'm wrong in my conclusions. ** How

[openstack-dev] [Blazar] Design question regarding use of trusts for physical reservation

Hello, When Blazar was migrated to use trusts for physical host reservation (https://review.openstack.org/#/c/84158/), it required Blazar users to be able to manage host aggregates (which is not allowed by default Nova policies). I believe that is not a good approach because it would allow them

[openstack-dev] [OSSN 0065] Users of Glance may be able to replace active image data

Users of Glance may be able to replace active image data --- ### Summary ### When Glance has been configured with the "show_multiple_locations" option enabled with default policy for set and delete locations, it is possible for a non-admin user having write access to the image metadata to replace

Re: [openstack-dev] [OpenStack-docs] [docs] Docs meeting

Correction: 9th of February. Apparently, I’m not very good at emails lately. Thank you, Andreas ;) From: Alexandra Settle Date: Thursday, February 9, 2017 at 10:36 AM To: "openstack-d...@lists.openstack.org" , "OpenStack Development

[openstack-dev] [docs] Docs meeting

Hello everyone, Your friendly neighbourhood PTL reminder that the weekly OpenStack manuals (docs) IRC meeting will be Thursday, 9th of January at 2100 UTC in in the #openstack-meeting-alt channel:

[openstack-dev] [Dragonflow] Nominating Xiao Hong Hui for core of Dragonflow

Hello, I would like to nominate Xiao Hong Hui as a core reviewer for Dragonflow. Since he has joined, Xiao has helped move the project forwards with important commits and very helpful reviews. He has shown great knowledge in Dragonflow, Openstack, and python. Please voice your opinion. If there

Re: [openstack-dev] [karbor][stackalytics] Karbor Missing Commits in Stackalytics

After the rename of Nimble to Mogan, all git-related stats are lost as well. http://stackalytics.com/?metric=commits_type= openstack-others=mogan Ilya, Can you please assist with rectifying this? On Thu, Feb 9, 2017 at 5:00 PM, Thierry Carrez wrote: > Yuval Brik wrote:

Re: [openstack-dev] [release] Support phase clarification

Just copy statement from http://docs.openstack.org/project-team-guide/stable-branches.html#support-phases "*The exact length of any given stable branch life support is discussed amongst stable branch maintainers and QA/infrastructure teams at every Design Summit*. It is generally between 9 and 15

Re: [openstack-dev] [karbor][stackalytics] Karbor Missing Commits in Stackalytics

Yuval Brik wrote: > By looking > at > http://stackalytics.com/?metric=commits=all_type=all=karbor > > I > noticed that Karbor has only 195 commits in Stackalytics, while in fact, > it has 721 commits (438 of them are not Jenkin's

[openstack-dev] [tripleo][kolla][openstack-helm][kuryr] OpenStack on containers leaveraging kuryr

Greetings, I was talking with Tony and he mentioned that he's recording a new demo for kuryr and, well, it'd be great to also use the containerized version of TripleO for the demo. His plan is to have this demo out by next week and that may be too tight for the containerized version of TripleO