[openstack-dev] [tripleo] releasing tripleoclient final (pike)

Hi! This week is pike-3 milestone and also final release for clients, which means we're going to cut a stable/pike branch for python-tripleoclient. It will be done by https://review.openstack.org/#/c/486657/ before Wednesday EOD - please ping me if any blocker. Once this is released, we'll

Re: [openstack-dev] [TripleO] breaking changes, new container image parameter formats

>>... >>DockerInsecureRegistryAddress: 172.19.0.2:8787/tripleoupstream >>DockerKeystoneImage: 172.19.0.2:8787/tripleoupstream/centos-binary- >> keystone:latest >>... That's strange construction, are you sure guys that you don't want to separate address:port from namespace?

Re: [openstack-dev] [oslo.db] [ndb] ndb namespace throughout openstack projects

On Mon, Jul 24, 2017 at 5:10 PM, Octave J. Orgeron wrote: > I don't think it makes sense to make these global. We don't need to change > all occurrences of String(255) to TinyText for example. We make that > determination through understanding the table structure and

Re: [openstack-dev] [oslo.db] [ndb] ndb namespace throughout openstack projects

Hi Michael, Comments below.. On 7/24/2017 2:49 PM, Michael Bayer wrote: On Mon, Jul 24, 2017 at 3:37 PM, Octave J. Orgeron wrote: For these, here is a brief synopsis: AutoStringTinyText, will convert a column to the TinyText type. This is used for cases where a

Re: [openstack-dev] [oslo.db] [ndb] ndb namespace throughout openstack projects

On Mon, Jul 24, 2017 at 3:37 PM, Octave J. Orgeron wrote: > For these, here is a brief synopsis: > > AutoStringTinyText, will convert a column to the TinyText type. This is used > for cases where a 255 varchar string needs to be converted to a text blob to > make the

Re: [openstack-dev] [oslo.db] [ndb] ndb namespace throughout openstack projects

Hi Michael, Comments below.. On 7/24/2017 9:13 AM, Michael Bayer wrote: On Mon, Jul 24, 2017 at 10:01 AM, Jay Pipes wrote: I would much prefer to *add* a brand new schema migration that handles conversion of the entire InnoDB schema at a certain point to an

Re: [openstack-dev] [oslo.db] [ndb] ndb namespace throughout openstack projects

Hi Jay, Comments below.. On 7/24/2017 8:01 AM, Jay Pipes wrote: +Dan Smith Good morning Mike :) Comments inline... On 07/23/2017 08:05 PM, Michael Bayer wrote: On Sun, Jul 23, 2017 at 6:10 PM, Jay Pipes wrote: Glad you brought this up, Mike. I was going to start a

Re: [openstack-dev] [oslo.db] [ndb] ndb namespace throughout openstack projects

Hi Jay, Comments below.. Thanks, Octave On 7/23/2017 4:10 PM, Jay Pipes wrote: Glad you brought this up, Mike. I was going to start a thread about this. Comments inline. On 07/23/2017 05:02 PM, Michael Bayer wrote: I've been working with Octave Oregon in assisting with new rules and

Re: [openstack-dev] [oslo.db] [ndb] ndb namespace throughout openstack projects

Hi Mike, Thanks for putting this together. Comments below.. Thanks, Octave On 7/23/2017 3:02 PM, Michael Bayer wrote: I've been working with Octave Oregon in assisting with new rules and datatypes that would allow projects to support the NDB storage engine with MySQL. To that end, we've made

Re: [openstack-dev] [docs][neutron] doc-migration status

2017-07-24 23:44 GMT+09:00 Doug Hellmann : > Excerpts from Kevin Benton's message of 2017-07-23 14:19:51 -0700: >> Yeah, the networking guide does include configuration for some of the >> sub-projects (e.g. BGP is at [1]). For the remaining ones there is work >> that needs

Re: [openstack-dev] help required regarding devstack

Also see - https://docs.openstack.org/devstack/latest/systemd.html On 07/24/2017 02:09 PM, Kristi Nikolla wrote: > Hi, > > I do not know about VM migration, however for restarting nova the right > service names are devstack@n-api, devstack@n-cpu, etc. > > ubuntu@k2k1:~$ systemctl list-units |

[openstack-dev] [ironic] this week's priorities and subteam reports

Hi, We are glad to present this week's priorities and subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. This Week's Priorities (as of the weekly ironic meeting) 1. Docs due to the

Re: [openstack-dev] help required regarding devstack

Hi, I do not know about VM migration, however for restarting nova the right service names are devstack@n-api, devstack@n-cpu, etc. ubuntu@k2k1:~$ systemctl list-units | grep devstack devstack@c-api.service loaded active running Devstack

Re: [openstack-dev] [tricircle]

Hi Meher, Can you include the paste for this? Can you also verify that your global-requirements file contains the tricircleclient module[1]?. It seems like the pip_install_gr function [2][3] is not resolving [4] the tricircleclient module[5] Regards, Victor Morales [1]

Re: [openstack-dev] [oslo] trying to understand CORS deprecation

On 07/24/2017 12:43 PM, Sean Dague wrote: I'm trying to knock out common deprecation messages which are generating noise in the test runs. There is a deprecation message emitted all the time during test runs in Nova which is: DeprecationWarning: Method 'CORS.set_latent()' has moved to

[openstack-dev] [oslo] trying to understand CORS deprecation

I'm trying to knock out common deprecation messages which are generating noise in the test runs. There is a deprecation message emitted all the time during test runs in Nova which is: DeprecationWarning: Method 'CORS.set_latent()' has moved to 'method.set_defaults()': CORS.set_latent has been

Re: [openstack-dev] [ironic] Looking for a good end-to-end demo of ironic integrated within openstack

Hey Greg, The Ironic deploy agent images are ramdisk images which include the ironic-python-agent https://docs.openstack.org/ironic-python-agent/latest/ Which is a tool build by the ironic team and used by ironic to deploy and cleanup the baremetal nodes. The cirros images are just the

Re: [openstack-dev] [ironic] Looking for a good end-to-end demo of ironic integrated within openstack

Hey Lucas, Thanks for the pointer to this ironic devstack setup using VMs as baremetal servers. I was able to follow the recipe and get this working and play with ironic. Of course I’ve got some follow up questions. Questions on the images: stack@devstack-ironic:~/devstack$ glance image-list

Re: [openstack-dev] [all] [oslo.db] [relational database users] heads up for a MariaDB issue that will affect most projects

hey good news, the owner of the issue upstream found that the SQL standard agrees with my proposed behavior. So while this is current MariaDB 10.2 / 10.3 behavior, hopefully it will be resolved in an upcoming release within those series. not sure of the timing though so we may not be able to

Re: [openstack-dev] [all] [oslo.db] [relational database users] heads up for a MariaDB issue that will affect most projects

On Mon, Jul 24, 2017 at 10:37 AM, Doug Hellmann wrote: > Excerpts from Michael Bayer's message of 2017-07-23 16:39:20 -0400: >> Hey list - >> >> It appears that MariaDB as of version 10.2 has made an enhancement >> that overall is great and fairly historic in the MySQL

Re: [openstack-dev] [oslo.db] [ndb] ndb namespace throughout openstack projects

On Mon, Jul 24, 2017 at 10:01 AM, Jay Pipes wrote: > I would much prefer to *add* a brand new schema migration that handles > conversion of the entire InnoDB schema at a certain point to an > NDB-compatible one *after* that point. That way, we isolate the NDB changes > to one

Re: [openstack-dev] [docs][neutron] doc-migration status

Excerpts from Kevin Benton's message of 2017-07-23 14:19:51 -0700: > Yeah, the networking guide does include configuration for some of the > sub-projects (e.g. BGP is at [1]). For the remaining ones there is work > that needs to be done because their docs live in wiki pages. > > 1. >

Re: [openstack-dev] [all] [oslo.db] [relational database users] heads up for a MariaDB issue that will affect most projects

Excerpts from Michael Bayer's message of 2017-07-23 16:39:20 -0400: > Hey list - > > It appears that MariaDB as of version 10.2 has made an enhancement > that overall is great and fairly historic in the MySQL community, > they've made CHECK constraints finally work. For all of MySQL's >

Re: [openstack-dev] [oslo.db] [ndb] ndb namespace throughout openstack projects

> So, I see your point here, but my concern here is that if we *modify* an > existing schema migration that has already been tested to properly apply > a schema change for MySQL/InnoDB and PostgreSQL with code that is > specific to NDB, we introduce the potential for bugs where users report > that

Re: [openstack-dev] [oslo.db] [ndb] ndb namespace throughout openstack projects

+Dan Smith Good morning Mike :) Comments inline... On 07/23/2017 08:05 PM, Michael Bayer wrote: On Sun, Jul 23, 2017 at 6:10 PM, Jay Pipes wrote: Glad you brought this up, Mike. I was going to start a thread about this. Comments inline. On 07/23/2017 05:02 PM, Michael

[openstack-dev] [tricircle]

Hello to the community of Openstack-Tricircle, I hope you are all well! I postulated the problem that I encountered during the trial of "Single pod installation with DevStack", I managed to deploy the solution by trying the install on Ubuntu and not on RHEL. Now I try "Multi-pod Installation

[openstack-dev] help required regarding devstack

Dear, I am a PhD candidate at COMSATS, lahore, Pakistan. I am working on devstack. Just wanted to know whether it supports VM Migration between two devstacks installed on two different physical machines as currently I am unable to find any lead. Also please let me know how to restart a particular

Re: [openstack-dev] [TripleO] breaking changes, new container image parameter formats

On 19.7.2017 14:41, Dan Prince wrote: I wanted to give a quick heads up on some breaking changes that started landing last week with regards to how container images are specified with Heat parameters in TripleO. There are a few patches associated with converting over to the new changes but the

Re: [openstack-dev] [TripleO] An experiment with Ansible

On Mon, Jul 24, 2017 at 3:12 AM, Marios Andreou wrote: > > > On Fri, Jul 21, 2017 at 1:21 AM, James Slagle > wrote: >> >> Following up on the previous thread: >> http://lists.openstack.org/pipermail/openstack-dev/2017-July/119405.html >> >> I wanted

Re: [openstack-dev] [TripleO] Migration from Neutron ML2OVS to OVN

On Wed, Jul 19, 2017 at 11:37 PM, Ben Nemec wrote: > > > On 07/18/2017 08:18 AM, Numan Siddique wrote: > >> >> >> On Thu, Jul 13, 2017 at 3:02 PM, Saravanan KR > > wrote: >> >> On Tue, Jul 11, 2017 at 11:40 PM, Ben

Re: [openstack-dev] [nova] placement/resource providers update 29

On Sat, 22 Jul 2017, Matt Riedemann wrote: On 7/21/2017 6:54 AM, Chris Dent wrote: ## Custom Resource Classes for Ironic A spec for custom resource classes is being updated to reflect the need to update the flavor and allocations of a previously allocated ironic node that how has a custom

Re: [openstack-dev] [TripleO][keystone] internal endpoints vs sanity

On 07/24/2017 04:23 PM, Attila Fazekas wrote: Thanks for your answer. The real question is do we agree in the internalULR usage what suggested in [1] is a bad security practice and should not be told to operators at all. Also we should try to get rid off the enpointTypes in keystone v4. Do we

Re: [openstack-dev] [TripleO][keystone] internal endpoints vs sanity

These questions are to the operators, and should be asked on openstack-operators IMO (maybe with tuning the overall tone to be a bit less aggressive). On 07/24/2017 10:23 AM, Attila Fazekas wrote: Thanks for your answer. The real question is do we agree in the internalULR usage what suggested

Re: [openstack-dev] [tripleo] Proposing Saravanan KR core

+1! On 21 July 2017 at 16:01, Emilien Macchi wrote: > Saravanan KR has shown an high level of expertise in some areas of > TripleO, and also increased his involvement over the last months: > - Major contributor in DPDK integration > - Derived parameter works > - and a lot of

Re: [openstack-dev] [TripleO][keystone] internal endpoints vs sanity

Thanks for your answer. The real question is do we agree in the internalULR usage what suggested in [1] is a bad security practice and should not be told to operators at all. Also we should try to get rid off the enpointTypes in keystone v4. Do we have any good (not just making happy funny dev

[openstack-dev] [swift] [oslo] [osprofiler] [performance] OSprofiler in Swift

Hello folks, I'm sending this email for asking about the works in integrating OSprofiler into Swift. Currently I'm working on this and the patches in Swift is waiting for review here: https://review.openstack.org/#/c/468316/ We knew that Swift has xprofile module [3] to do profiling works.

Re: [openstack-dev] [tripleo] Proposing Saravanan KR core

On Mon, Jul 24, 2017 at 12:10 PM, Marios Andreou wrote: > > > On Fri, Jul 21, 2017 at 6:01 PM, Emilien Macchi > wrote: > >> Saravanan KR has shown an high level of expertise in some areas of >> TripleO, and also increased his involvement over the last

Re: [openstack-dev] [tripleo] Proposing Bogdan Dobrelya core on TripleO / Containers

On Fri, Jul 21, 2017 at 5:55 PM, Emilien Macchi wrote: > Hi, > > Bogdan (bogdando on IRC) has been very active in Containerization of > TripleO and his quality of review has increased over time. > I would like to give him core permissions on container work in TripleO. > Any

Re: [openstack-dev] [TripleO] An experiment with Ansible

On Fri, Jul 21, 2017 at 1:21 AM, James Slagle wrote: > Following up on the previous thread: > http://lists.openstack.org/pipermail/openstack-dev/2017-July/119405.html > > I wanted to share some work I did around the prototype I mentioned > there. I spent a couple days

Re: [openstack-dev] [oslo.db] [ndb] ndb namespace throughout openstack projects

On 07/24/2017 08:05 AM, Michael Bayer wrote: On Sun, Jul 23, 2017 at 6:10 PM, Jay Pipes wrote: Glad you brought this up, Mike. I was going to start a thread about this. Comments inline. On 07/23/2017 05:02 PM, Michael Bayer wrote: Well, besides that point (which I agree

Re: [openstack-dev] [tripleo] Proposing Saravanan KR core

On Fri, Jul 21, 2017 at 6:01 PM, Emilien Macchi wrote: > Saravanan KR has shown an high level of expertise in some areas of > TripleO, and also increased his involvement over the last months: > - Major contributor in DPDK integration > - Derived parameter works > - and a lot