Re: [openstack-dev] [keystone][nova] Persistent application credentials

On Mon, Jul 17, 2017 at 6:39 PM, Zane Bitter wrote: > So the application credentials spec has merged - huge thanks to Monty and > the Keystone team for getting this done: > > https://review.openstack.org/#/c/450415/ > http://specs.openstack.org/openstack/keystone-specs/specs/

[openstack-dev] [tripleo] [kolla] [rdo] EPEL and RDO in Kolla containers

Hi, Just FYI... I took a bit of time to document what seems to be most (if not all) dependencies that vanilla Kolla currently pulls from EPEL on CentOS Binary builds. This list is documented here [1]. TripleO doesn't use all the CentOS binary containers from Kolla, only a subset of those is

Re: [openstack-dev] [OpenStack-Infra] [infra][nova] Corrupt nova-specs repo

On 2017-06-30 16:11:42 +1000 (+1000), Ian Wienand wrote: > Unfortunately it seems the nova-specs repo has undergone some > corruption, currently manifesting itself in an inability to be pushed > to github for replication. [...] > So you may notice this is refs/changes/26/463526/[2-9] > > Just

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

I re-read this and maybe you mean, some containers will live only outside of k8s and some will live in k8s, not that you want to to support not having k8s at all with the same code base? That would be a much easier thing, and agree ansible would be very good at that. Thanks, Kevin

Re: [openstack-dev] git review -d + git rebase changing author?

On Tue, 18 Jul 2017 09:22:31 +0900, Ghanshyam Mann wrote: Yes, this is same case when we do fetch patch set using git checkout, i do not think its something to do with gite review -d. Doing that shouldn't change the author, at least in my experience. I constantly 'git fetch' or 'git review -d

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

I think thats a good question without an easy answer. I think TripleO's own struggle with orchestration has shown that its maybe one of the hardest pieces. There are a lot of orchestration tools out there. Each has its strengths/weaknesses. I personally can't really pick what the best one is

Re: [openstack-dev] git review -d + git rebase changing author?

On Tue, Jul 18, 2017 at 8:24 AM, Matt Riedemann wrote: > I don't have a strict recreate on this right now, but wanted to bring it up > in case others have seen it. I've done this unknowingly and seen it happen > to other changes, like: > >

Re: [openstack-dev] git review -d + git rebase changing author?

On 2017-07-17 18:24:39 -0500 (-0500), Matt Riedemann wrote: > I don't have a strict recreate on this right now, but wanted to bring it up > in case others have seen it. [...] Any chance you can find the author change in your git reflog? -- Jeremy Stanley

Re: [openstack-dev] [infra][devstack] DIB builds after mysql.qcow2 removal

On 07/18/2017 10:01 AM, Tony Breeds wrote: It wasn't forgotten as suchi, there are jobs still using it/them. If keeping the branches around cuases bigger probelsm then EOLing them is fine. I'll try to generate a list of the affected projects/jobs and turn them off. Thanks; yeah this was

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

On Mon, Jul 17, 2017 at 10:13 AM, Emilien Macchi wrote: > On Mon, Jul 17, 2017 at 5:32 AM, Flavio Percoco wrote: > > On 14/07/17 08:08 -0700, Emilien Macchi wrote: > >> > >> On Fri, Jul 14, 2017 at 2:17 AM, Flavio Percoco > wrote: > >>>

Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

On Mon, Jul 17, 2017 at 07:09:13PM +0200, Andreas Jaeger wrote: > On 2017-07-17 15:51, Andy McCrae wrote: > > We held back the openstack-ansible repo to allow us to point to the > > mitaka-eol tag for the other role/project repos. > > That's been done - I've created the mitaka-eol tag in the > >

Re: [openstack-dev] [infra][devstack] DIB builds after mysql.qcow2 removal

On Mon, Jul 17, 2017 at 07:22:34PM +1000, Ian Wienand wrote: > I have taken the liberty of EOL-ing stable/liberty and stable/mitaka > for devstack. I get the feeling it was just forgotten at the time. > Comments in [4] support this theory. I have also taken the liberty of > approving backports

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

I think if you try to go down the Kubernetes & !Kubernetes path, you'll end up re-implementing pretty much all of Kubernetes, or you will use Kubernetes just like !Kubernetes and gain very little benefit from it. Thanks, Kevin From: Flavio Percoco

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

We do support some upstream charts but we started mariadb/rabbit before some of the upstream charts were written, so we duplicate a little bit of functionality at the moment. You can mix and match though. If an upstream chart doesn't work with kolla-kubernetes, I consider that a bug we should

[openstack-dev] [keystone][nova] Persistent application credentials

So the application credentials spec has merged - huge thanks to Monty and the Keystone team for getting this done: https://review.openstack.org/#/c/450415/ http://specs.openstack.org/openstack/keystone-specs/specs/keystone/pike/application-credentials.html However, it appears that there was a

[openstack-dev] git review -d + git rebase changing author?

I don't have a strict recreate on this right now, but wanted to bring it up in case others have seen it. I've done this unknowingly and seen it happen to other changes, like: https://review.openstack.org/#/c/428241/7..8//COMMIT_MSG https://review.openstack.org/#/c/327564/3..4//COMMIT_MSG

Re: [openstack-dev] [openstack-ansible] restrictive umask / file permissions in target hosts

On 07/04/2017 03:54 AM, Markus Zoeller wrote: > How do you deal with hosts which have a restrictive umask of 077 > *before* openstack-ansible starts the setup? Do you start with the > default umask of 022 and opt-in later to that security hardening[1]? We don't test for that in the

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

> I think this at some point might be single biggest benefit of using > helm on the long run - leverage infrastructure charts that aren't > openstack-centric. Things like etcd are already written and > potentially we can just help support them. I think the tools that are being discussion here are

[openstack-dev] [os-upstream-institute] Meeting Cancelled

Hello Everyone! We will not be having our meeting today at 20:00 UTC because there isn't much on the agenda :) If there is something you want to discuss, please drop into the #openstack-upstream-insutute channel and ping us. Enjoy your extra hour! -Kendall Nelson (diablo_rojo)

[openstack-dev] Election Season, PTL July/August 2017

Hello Everyone! Election details: https://governance.openstack.org/election/ Please read the stipulations and timelines for candidates and electorate contained in this governance documentation. Be aware, in the PTL elections if the program only has one candidate, that candidate is acclaimed and

Re: [openstack-dev] [nova]notification update week 29

On 7/17/2017 2:36 AM, Balazs Gibizer wrote: Hi, Here is the status update / focus setting mail about notification work for week 29. Bugs [Undecided] https://bugs.launchpad.net/nova/+bug/1684860 Versioned server notifications don't include updated_at The fix

[openstack-dev] [keystone] feature freeze and spec status

Hi all, I wanted to send a friendly reminder that feature freeze for keystone will be in R-5 [0], which is the end of next week. That leaves just under 10 business days for feature work (8 considering the time to get through the gate). Of the specifications we've committed to for Pike, the

Re: [openstack-dev] [tripleo] weekly meetings on #tripleo

Since we have mixed feelings but generally agree that we should give it a try, let's give it a try and see how it goes, at least one time, tomorrow. On Mon, Jul 10, 2017 at 10:01 AM, Michele Baldessari wrote: > On Mon, Jul 10, 2017 at 11:36:03AM -0230, Brent Eagles wrote: >>

[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] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

On 17 July 2017 at 10:13, Emilien Macchi wrote: > On Mon, Jul 17, 2017 at 5:32 AM, Flavio Percoco wrote: >> On 14/07/17 08:08 -0700, Emilien Macchi wrote: >>> >>> On Fri, Jul 14, 2017 at 2:17 AM, Flavio Percoco wrote:

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

On Mon, Jul 17, 2017 at 5:32 AM, Flavio Percoco wrote: > On 14/07/17 08:08 -0700, Emilien Macchi wrote: >> >> On Fri, Jul 14, 2017 at 2:17 AM, Flavio Percoco wrote: >>> >>> >>> Greetings, >>> >>> As some of you know, I've been working on the second phase of

Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

On 2017-07-17 15:51, Andy McCrae wrote: > We held back the openstack-ansible repo to allow us to point to the > mitaka-eol tag for the other role/project repos. > That's been done - I've created the mitaka-eol tag in the > openstack-ansible repo, can we remove the stable/mitaka branch from >

Re: [openstack-dev] [infra][ironic] Patch needed to merge to fix ironic-inspector grenade job

John++ Thanks for looking into this! -- milan po 17. 7. 2017 v 17:13 odesílatel John Villalovos < openstack@sodarock.com> napsal: > Hi Infra, > > We were hoping to get a review of: > https://review.openstack.org/483059 > Add the ironic-inspector services to features.yaml >

[openstack-dev] [tripleo] release reminders

A few reminders for our dear TripleO community about releases that are coming: - pike-3 will be released by the end of next week: https://releases.openstack.org/pike/schedule.html#p-3 - because we're using release:cycle-trailing model, it means our Feature Freeze will happen during Aug 07 - Aug

Re: [openstack-dev] [nova][placement] scheduling with custom resouce classes

On 07/17/2017 11:31 AM, Balazs Gibizer wrote: On Thu, Jul 13, 2017 at 11:37 AM, Chris Dent wrote: On Thu, 13 Jul 2017, Balazs Gibizer wrote: /placement/allocation_candidates?resources=CUSTOM_MAGIC%3A512%2CMEMORY_MB%3A64%2CVCPU%3A1" but placement returns an empty

[openstack-dev] [all][ptl][tc] IMPORTANT upcoming change to technical elections

For those who won't read the giant wall of text below, a quick summary... If you want to run or vote in upcoming elections for PTL and TC, make sure your Foundation Individual Membership is active and has at least one Email address which matches an Email address in your Gerrit account: log in at

Re: [openstack-dev] [tripleo] scenario006 conflict

On Mon, Jul 17, 2017 at 9:04 AM, Michele Baldessari wrote: > On Wed, Jul 12, 2017 at 02:23:25PM -0700, Emilien Macchi wrote: >> Hey folks, >> >> Derek, it seems like you want to deploy Ironic on scenario006 >> (https://review.openstack.org/#/c/474802). I was wondering how it

Re: [openstack-dev] [Glare] Application for inclusion of Glare in the list of official projects - Answers

On 17/07/17 12:34 +0300, Mikhail Fedosin wrote: Hello! Thank you all for your answers and advises! I will try to summarize all of the above. The purpose of the application was to get the community's views on including Glare in the list of official projects, and a potential replacement of

Re: [openstack-dev] [nova][placement] scheduling with custom resouce classes

On Thu, Jul 13, 2017 at 11:37 AM, Chris Dent wrote: On Thu, 13 Jul 2017, Balazs Gibizer wrote: /placement/allocation_candidates?resources=CUSTOM_MAGIC%3A512%2CMEMORY_MB%3A64%2CVCPU%3A1" but placement returns an empty response. Then nova scheduler falls back to legacy

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

On 17/07/17 09:47 -0400, James Slagle wrote: On Mon, Jul 17, 2017 at 8:05 AM, Flavio Percoco wrote: Thanks for all the feedback so far. This is one of the things I appreciate the most about this community, Open conversations, honest feedback and will to collaborate. I'm

Re: [openstack-dev] [tripleo] scenario006 conflict

On 17/07/17 15:56 +0100, Derek Higgins wrote: On 17 July 2017 at 15:37, Emilien Macchi wrote: On Thu, Jul 13, 2017 at 6:01 AM, Emilien Macchi wrote: On Thu, Jul 13, 2017 at 1:55 AM, Derek Higgins wrote: On 12 July 2017 at 22:33,

[openstack-dev] [oslo] PTL nominations

Hi oslo folks, The PTL nomination week is fast approaching [0], and as you might have guessed by the subject of this email, I am not planning to run for Queens, I'm still in the team and give some guidance about oslo PTL's daily work as previous PTL did before . It' my honor to be oslo PTL, I

[openstack-dev] [infra][ironic] Patch needed to merge to fix ironic-inspector grenade job

Hi Infra, We were hoping to get a review of: https://review.openstack.org/483059 Add the ironic-inspector services to features.yaml openstack-infra/devstack-gate As it is needed to fix the ironic-inspector grenade job. Thanks, John

Re: [openstack-dev] [all] Queens Goal for policy-in-code

On Wed, Jul 12, 2017 at 7:31 AM, Lance Bragstad wrote: > [...] I can look into organizing a slot at the PTG so we can work through > things as a group. Good idea! In our experience from our last PTG, having one room for each goal was a bit overkill and the room was

Re: [openstack-dev] [oslo][all] next week is deadline for final release for non-client libraries

We scheduled the final release(s) for oslo libraries on July 19, please focus on bug fixing. thanks 2017-07-14 20:48 GMT+08:00 ChangBo Guo : > Just a reminder, I will add final releases of oslo libraries for Pike on > next Monday. > > 2017-07-10 22:37 GMT+08:00 ChangBo Guo

Re: [openstack-dev] [tripleo] scenario006 conflict

On 17 July 2017 at 15:37, Emilien Macchi wrote: > On Thu, Jul 13, 2017 at 6:01 AM, Emilien Macchi wrote: >> On Thu, Jul 13, 2017 at 1:55 AM, Derek Higgins wrote: >>> On 12 July 2017 at 22:33, Emilien Macchi wrote:

Re: [openstack-dev] [tripleo] scenario006 conflict

On Thu, Jul 13, 2017 at 6:01 AM, Emilien Macchi wrote: > On Thu, Jul 13, 2017 at 1:55 AM, Derek Higgins wrote: >> On 12 July 2017 at 22:33, Emilien Macchi wrote: >>> On Wed, Jul 12, 2017 at 2:23 PM, Emilien Macchi

Re: [openstack-dev] [all][stable][ptls] Tagging mitaka as EOL

Hi Andreas, OK, added. I'm waiting for packstack confirmation. > > The current list is now: > > > openstack/sahara-extra stable/icehousePlease retire > openstack/sahara-extra stable/mitaka Please retire > openstack/packstack stable/kiloWaiting for

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

On Mon, Jul 17, 2017 at 8:05 AM, Flavio Percoco wrote: > Thanks for all the feedback so far. This is one of the things I appreciate > the > most about this community, Open conversations, honest feedback and will to > collaborate. > > I'm top-posting to announce that we'll have

Re: [openstack-dev] [infra][devstack] DIB builds after mysql.qcow2 removal

On Mon, Jul 17, 2017 at 07:22:34PM +1000, Ian Wienand wrote: > Hi, > > The removal of the mysql.qcow2 image [1] had a flow-on effect noticed > first by Paul in [2] that the tools/image_list.sh "sanity" check was > not updated, leading to DIB builds failing in a most unhelpful way as > it tries to

[openstack-dev] [magnum] Interface configuration and assumptions for masters/minions launched by magnum

When MAGNUM launches a VM or Ironic instance for a COE master or minion node, with the COE Image, What is the interface configuration and assumptions for these nodes ? e.g. - only a single interface ? - master and minion communication over that interface ? - communication to Docker Registry or

[openstack-dev] [magnum] Architecture support for either VM or Ironic instance as Containers' Host ?

I believe the MAGNUM architecture supports using either a VM Instance or an Ironic Instance as the Host for the COE’s masters and minions. How is this done / abstracted within the MAGNUM Architecture ? i.e. is there a ‘container-host-driver API’ that is defined; and implemented for both VM and

Re: [openstack-dev] [TripleO] Forming our plans around Ansible

On 07/12/2017 04:18 AM, Steve Baker wrote: On Wed, Jul 12, 2017 at 11:47 AM, James Slagle > wrote: On Tue, Jul 11, 2017 at 6:53 PM, Steve Baker > wrote: > > > On Tue,

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

On 14/07/17 08:08 -0700, Emilien Macchi wrote: On Fri, Jul 14, 2017 at 2:17 AM, Flavio Percoco wrote: Greetings, As some of you know, I've been working on the second phase of TripleO's containerization effort. This phase if about migrating the docker based deployment onto

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

Thanks for all the feedback so far. This is one of the things I appreciate the most about this community, Open conversations, honest feedback and will to collaborate. I'm top-posting to announce that we'll have a joint meeting with the Kolla team on Wednesday at 16:00 UTC. I know it's not an

[openstack-dev] [tripleo] CI Squad Meeting Summary (week 28) - some announcements

If the topics below interest you and you want to contribute to the discussion, feel free to join the next meeting: Time: Thursdays, 14:30-15:30 UTC Place: https://bluejeans.com/4113567798/ Full minutes: https://etherpad.openstack.org/p/tripleo-ci-squad-meeting = Announcements = TripleO Cores

Re: [openstack-dev] [horizon] [horizon-plugin] Raising Django version cap

Awesome, I appreciate the work here. I spoke with a couple Django folk on IRC and they didn’t have any other solution than “vendor the code”, so I think your approach is probably the most reasonable. I’m fairly annoyed that they dropped an interface like that, but oh well. I’ll take a look at

[openstack-dev] [Glare] Application for inclusion of Glare in the list of official projects - Answers

Hello! Thank you all for your answers and advises! I will try to summarize all of the above. The purpose of the application was to get the community's views on including Glare in the list of official projects, and a potential replacement of Glance in the foreseeable future. A large number of

[openstack-dev] [infra][devstack] DIB builds after mysql.qcow2 removal

Hi, The removal of the mysql.qcow2 image [1] had a flow-on effect noticed first by Paul in [2] that the tools/image_list.sh "sanity" check was not updated, leading to DIB builds failing in a most unhelpful way as it tries to cache the images for CI builds. So while [2] fixes the problem; one

Re: [openstack-dev] [Vitrage] Collectd notification isn't shown on the Vitrage Graph

Hi Volodymyr, Thinking about this again, I understand that Vitrage is not supposed to use the Collectd message as part of the alarm unique key. We currently have a bug with clearing Collectd alarms, as a result of the Vitrage ID refactoring that happened in Pike. Until we fix it, you can you

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

On 14.7.2017 23:00, Ben Nemec wrote: On 07/14/2017 11:43 AM, Joshua Harlow wrote: Out of curiosity, since I keep on hearing/reading all the tripleo discussions on how tripleo folks are apparently thinking/doing? redesigning the whole thing to use ansible + mistral + heat, or ansible +

Re: [openstack-dev] [horizon] [horizon-plugin] Raising Django version cap

Was hoping to play with this much sooner, but here is a quick hack for horizon working with django 1.11 https://review.openstack.org/#/c/484277/ The main issues are with widgets from Django which are no longer there, and all I've done is move them to our repo from django 1.10's code. This is

Re: [openstack-dev] [TripleO] Let's use Ansible to deploy OpenStack services on Kubernetes

On 14.07.2017 22:55, Fox, Kevin M wrote: > Part of the confusion I think is in the different ways helm can be used. > > Helm can be used to orchestrate the deployment of a whole service (ex, nova). > "launch these 3 k8s objects, template out this config file, run this job to > init the db, or

[openstack-dev] [nova]notification update week 29

Hi, Here is the status update / focus setting mail about notification work for week 29. Bugs [Undecided] https://bugs.launchpad.net/nova/+bug/1684860 Versioned server notifications don't include updated_at The fix https://review.openstack.org/#/c/475276/ is in focus but comments needs to

Re: [openstack-dev] [rpm-packaging][karbor]

Hi Chandan, Thank your work about packaging abclient . chenying 2017-07-14 16:29 GMT+08:00 Jiong Liu : > Message: 2 > Date: Fri, 14 Jul 2017 12:10:00 +0530 > From: Chandan kumar > To: "OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [tripleo] Deprecated Parameters Warning

Thanks Emilien. Now, the warning message for using a deprecated message is available for CLI. Sample message from CI [1] looks like below: 2017-07-14 19:45:09 | WARNING: Following parameters are deprecated and still defined. Deprecated parameters will be removed soon! 2017-07-14 19:45:09 |

Re: [openstack-dev] [tripleo] Deriving Parameters from Introspection Data

On Sun, Jul 16, 2017 at 6:10 AM, Don maillist wrote: > Looks interesting. Wish I had this or something like it now for Newton and > OVS 2.6.1 which just dropped. Wondering why you don't include the grub > command line? KernelArgs parameter which will have iommu and huge