Re: [openstack-dev] Storyboard python script

On 2018-10-31 22:39:01 + (+), Krishna Jain wrote: > I’m an animator with some coding experience picking up Python. I > came across your python-storyboardclient library, which would be > very helpful for automating our pipeline in Toon Boom Storyboard > Pro. [...] The

Re: [openstack-dev] [ironic] Team gathering at the Forum?

Hello Ironicers - We’ve booked the same venue for the Scientific SIG for Wednesday evening, and hopefully we’ll see you there. There’s plenty of cross-over between our groups, particularly at an operator level. Cheers, Stig > On 29 Oct 2018, at 14:58, Dmitry Tantsur wrote: > > Hi folks! >

Re: [openstack-dev] Storyboard python script

I believe this project is a client for Storyboard, an OpenStack project and not the commercial product you’re mentioning Sent from my iPhone > On Oct 31, 2018, at 11:39 PM, Krishna Jain wrote: > > Hi, > I’m an animator with some coding experience picking up Python. I came across > your

[openstack-dev] Storyboard python script

Hi, I’m an animator with some coding experience picking up Python. I came across your python-storyboardclient library, which would be very helpful for automating our pipeline in Toon Boom Storyboard Pro. I’d like to have Python call some of the Javascript scripts I’ve written to extend SBPro.

Re: [openstack-dev] [tripleo] reducing our upstream CI footprint

On 10/31/18 4:59 PM, Harald Jensås wrote: On Wed, 2018-10-31 at 11:39 -0600, Wesley Hayutin wrote: On Wed, Oct 31, 2018 at 11:21 AM Alex Schultz wrote: Hey everyone, Based on previous emails around this[0][1], I have proposed a possible reducing in our usage by switching the

[openstack-dev] [tripleo] shutting down 3rd party TripleO CI for measurements

Greetings, The TripleO-CI team would like to consider shutting down all the third party check jobs running against TripleO projects in order to measure results with and without load on the cloud for some amount of time. I suspect we would want to shut things down for roughly 24-48 hours. If

Re: [openstack-dev] [tripleo] reducing our upstream CI footprint

On Wed, 2018-10-31 at 11:39 -0600, Wesley Hayutin wrote: > > > On Wed, Oct 31, 2018 at 11:21 AM Alex Schultz > wrote: > > Hey everyone, > > > > Based on previous emails around this[0][1], I have proposed a > > possible > > reducing in our usage by switching the scenario001--011 jobs to > >

Re: [openstack-dev] [manila][tc] Seeking feedback on the OpenStack cloud vision

On 24/10/18 11:14 -0400, Zane Bitter wrote: Greetings, Manila team! As you may be aware, I've been working with other folks in the community on documenting a vision for OpenStack clouds (formerly known as the 'Technical Vision') - essentially to interpret the mission statement in long-form,

[openstack-dev] [goal][python3] week 12 update

This is week 12 of the "Run under Python 3 by default" goal (https://governance.openstack.org/tc/goals/stein/python3-first.html). Observant readers will notice that the last update email was during week 9. I've been out for a couple of weeks, but you've all been busy in that time! == What we

Re: [openstack-dev] [all] Zuul job backlog

Hi All, I have fixed the glance functional test issue, patch [1] is merged in master. I hope the mentioned issue is now resolved. Kindly let me know. [1] https://review.openstack.org/#/c/608856/ Thank you, Abhishek On Mon, 8 Oct 2018 at 11:37 PM, Doug Hellmann wrote: > Abhishek Kekane

Re: [openstack-dev] [Edge-computing] [tripleo][FEMDC] IEEE Fog Computing: Call for Contributions - Deadline Approaching

> On 2018. Oct 31., at 19:11, Mike Bayer wrote: > > On Wed, Oct 31, 2018 at 10:57 AM Bogdan Dobrelya wrote: >> >> (cross-posting openstack-dev) >> >> Hello. >> [tl;dr] I'm looking for co-author(s) to come up with "Edge clouds data >> consistency requirements and challenges" a position paper

Re: [openstack-dev] [tripleo] Zuul Queue backlogs and resource usage

On Wed, 2018-10-31 at 11:35 -0600, Alex Schultz wrote: > On Wed, Oct 31, 2018 at 11:16 AM Harald Jensås > wrote: > > > > On Tue, 2018-10-30 at 15:00 -0600, Alex Schultz wrote: > > > On Tue, Oct 30, 2018 at 12:25 PM Clark Boylan < > > > cboy...@sapwetik.org> > > > wrote: > > > > > > > > On Tue,

Re: [openstack-dev] [tripleo] reducing our upstream CI footprint

Alex Schultz writes: > Hey everyone, > > Based on previous emails around this[0][1], I have proposed a possible > reducing in our usage by switching the scenario001--011 jobs to > non-voting and removing them from the gate[2]. This will reduce the > likelihood of causing gate resets and

Re: [openstack-dev] [Edge-computing] [tripleo][FEMDC] IEEE Fog Computing: Call for Contributions - Deadline Approaching

Hi, Thank you for sharing your proposal. I think this is a very interesting topic with a list of possible solutions some of which this group is also discussing. It would also be great to learn more about the IEEE activities and have experience about the process in this group on the way

Re: [openstack-dev] [tripleo] reducing our upstream CI footprint

On Wed, Oct 31, 2018 at 11:21 AM Alex Schultz wrote: > Hey everyone, > > Based on previous emails around this[0][1], I have proposed a possible > reducing in our usage by switching the scenario001--011 jobs to > non-voting and removing them from the gate[2]. This will reduce the > likelihood of

Re: [openstack-dev] [tripleo] Zuul Queue backlogs and resource usage

On Wed, Oct 31, 2018 at 11:16 AM Harald Jensås wrote: > > On Tue, 2018-10-30 at 15:00 -0600, Alex Schultz wrote: > > On Tue, Oct 30, 2018 at 12:25 PM Clark Boylan > > wrote: > > > > > > On Tue, Oct 30, 2018, at 10:42 AM, Alex Schultz wrote: > > > > On Tue, Oct 30, 2018 at 11:36 AM Ben Nemec < >

[openstack-dev] [tripleo] reducing our upstream CI footprint

Hey everyone, Based on previous emails around this[0][1], I have proposed a possible reducing in our usage by switching the scenario001--011 jobs to non-voting and removing them from the gate[2]. This will reduce the likelihood of causing gate resets and hopefully allow us to land corrective

Re: [openstack-dev] [tripleo] Zuul Queue backlogs and resource usage

On Tue, 2018-10-30 at 15:00 -0600, Alex Schultz wrote: > On Tue, Oct 30, 2018 at 12:25 PM Clark Boylan > wrote: > > > > On Tue, Oct 30, 2018, at 10:42 AM, Alex Schultz wrote: > > > On Tue, Oct 30, 2018 at 11:36 AM Ben Nemec < > > > openst...@nemebean.com> wrote: > > > > > > > > Tagging with

Re: [openstack-dev] [tripleo] request for feedback/review on docker2podman upgrade

Emilien Macchi writes: > A bit of an update here: > > - We merged the patch in openstack/paunch that stop the Docker container if > we try to start a Podman container. > - We switched the undercloud upgrade job to test upgrades from Docker to > Podman (for now containers are stopped in Docker

Re: [openstack-dev] [Edge-computing][tripleo][FEMDC] IEEE Fog Computing: Call for Contributions - Deadline Approaching

I forgot to mention the submission registration and abstract has to be submitted today. I've created it as #1570506394, and the paper itself can be uploaded until the Nov 8 (or Nov 9 perhaps as the registration system shows to me). I'm not sure that paper number is searchable publicly, so here

[openstack-dev] [tripleo] gate issues please do not approve/recheck

Hey folks, So we have identified an issue that has been causing a bunch of failures and proposed a revert of our podman testing[0]. We have cleared the gate and are asking that you not approve or recheck any patches at this time. We will let you know when it is safe to start approving things.

Re: [openstack-dev] Ironic integration CI jobs

On Wed, Oct 31, 2018 at 7:38 AM Dmitry Tantsur wrote: > [trim] > > > Ditto, grenade jobs do not cover our tests at all. Also this is the > very job we > > run on other projects (nova, neutron, maybe more), so it will be a > bit painful > > to remove it. > > > > > > We run the

Re: [openstack-dev] [Edge-computing][tripleo][FEMDC] IEEE Fog Computing: Call for Contributions - Deadline Approaching

(cross-posting openstack-dev) Hello. [tl;dr] I'm looking for co-author(s) to come up with "Edge clouds data consistency requirements and challenges" a position paper [0] (papers submitting deadline is Nov 8). The problem scope is synchronizing control plane and/or deployments-specific data

Re: [openstack-dev] Ironic integration CI jobs

On 10/31/18 2:57 PM, Julia Kreger wrote: On Wed, Oct 31, 2018 at 5:44 AM Dmitry Tantsur > wrote: Hi, On 10/31/18 1:36 AM, Julia Kreger wrote: [trim] > > ironic-tempest-dsvm-ipa-wholedisk-agent_ipmitool-tinyipa-multinode - This job is

Re: [openstack-dev] Sharing upstream contribution mentoring result with Korea user group

That's great job Ian and team. It is really great when local user groups doing so much effort for upstream contribution mentoring. From FirstContact SIG point of view, feel free to let us know any help you need in term of engaging new contributors with their interesting projects team and

Re: [openstack-dev] Ironic integration CI jobs

On Wed, Oct 31, 2018 at 5:44 AM Dmitry Tantsur wrote: > Hi, > > On 10/31/18 1:36 AM, Julia Kreger wrote: > [trim] > > > > ironic-tempest-dsvm-ipa-wholedisk-agent_ipmitool-tinyipa-multinode - > This job is > > essentially the same as our grenade mutlinode job, the only difference > being > >

Re: [openstack-dev] [NOVA] nova GPU suppot and find GPU type

On Tue, Oct 30, 2018 at 12:21 AM Manuel Sopena Ballesteros < manuel...@garvan.org.au> wrote: > Dear Nova community, > > > > This is the first time I work with GPUs. > > > > I have a Dell C4140 with x4 Nvidia Tesla V100 SXM2 16GB I would like to > setup on Openstack Rocky. > > > > I checked the

Re: [openstack-dev] [oslo] No complains about rabbitmq SSL problems: could we have this in the logs?

For what it’s worth: I ran into the same issue. I think the problem lies a bit deeper because it’s a problem with kombu as when debugging I saw that Oslo messaging tried to connect and hung after. Sent from my iPhone > On Oct 31, 2018, at 2:29 PM, Thomas Goirand wrote: > > Hi, > > It took

Re: [openstack-dev] Neutron stadium project Tempest plugins

On Wed, 24 Oct 2018 05:08:11 +0900 Slawomir Kaplonski wrote > Hi, > > Thx Miguel for raising this. > List of tempest plugins is on > https://docs.openstack.org/tempest/latest/plugin-registry.html - if URL for > Your plugin is the same as Your main repo, You should move Your

[openstack-dev] [oslo] No complains about rabbitmq SSL problems: could we have this in the logs?

Hi, It took me a long long time to figure out that my SSL setup was wrong when trying to connect Heat to rabbitmq over SSL. Unfortunately, Oslo (or heat itself) never warn me that something was wrong, I just got nothing working, and no log at all. I'm sure I wouldn't be the only one happy about

Re: [openstack-dev] Ironic integration CI jobs

Hi, On 10/31/18 1:36 AM, Julia Kreger wrote: With the discussion of CI jobs and the fact that I have been finding myself checking job status several times a day so early in the cycle, I think it is time for ironic to revisit many of our CI jobs. The bottom line is ironic is very resource

Re: [openstack-dev] Ironic integration CI jobs

On Tue, Oct 30, 2018 at 05:36:09PM -0700, Julia Kreger wrote: > ironic-tempest-dsvm-ipa-wholedisk-bios-agent_ipmitool-tinyipa - This job > essentially just duplicates the functionality already covered in other > jobs, including the grenade job. FYI this job runs in the Neutron check queue

Re: [openstack-dev] [tripleo][openstack-ansible][nova][placement] Owners needed for placement extraction upgrade deployment tooling

On Wed, 31 Oct 2018, Eduardo Gonzalez wrote: - Run db syncs as there is not command for that yet in the master branch - Apply upgrade process for db changes The placement-side pieces for this are nearly ready, see the stack beginning at https://review.openstack.org/#/c/611441/ -- Chris Dent

Re: [openstack-dev] [tripleo][openstack-ansible][nova][placement] Owners needed for placement extraction upgrade deployment tooling

Hi, from kolla side I've started the work. In kolla images [0] for now only placement is separated to an independent image, only source is code is being installed, binary still uses nova-placement packages until a binary package exists from the debian and centos families. In kolla-ansible [1]

[openstack-dev] Announcing OpenStack Cluster Installer (OCI)

Hi, After about 6 months of development, I'm proud to announce the first fully working version of OCI. Here's the description: OCI (OpenStack Cluster Installer) is a software to provision an OpenStack cluster automatically. This package install a provisioning machine, which consists of a DHCP

Re: [openstack-dev] [tripleo][openstack-ansible][nova][placement] Owners needed for placement extraction upgrade deployment tooling

On 30-10-18 14:29:12, Emilien Macchi wrote: > On the TripleO side, it sounds like Lee Yarwood is taking the lead with a > first commit in puppet-placement: > https://review.openstack.org/#/c/604182/ > > Lee, can you confirm that you and your team are working on it for Stein > cycle? ACK, just

Re: [openstack-dev] [vitrage] I have some problems with Prometheus alarms in vitrage.

Hi, > > This is strange. I would expect your original definition to work as well, > since the alarm key in Vitrage is defined by a combination of the alert > name and the instance. We will check it again. > BTW, we solved a different bug related to Prometheus alarms not being > cleared [1].