Re: [Openstack-operators] [User-committee] [scientific] 0900 UTC meeting time change?

Hi all, Review up for this: https://review.openstack.org/478317 Cheers, On 21 June 2017 at 18:54, Stig Telfer wrote: > Doing future meetings at 1100UTC would also be fine by me. I’ll put it on > the agenda for today’s meeting (in ~10 minutes) > > Stig > > > On 21

[Openstack-operators] [keystone] removing domain configuration upload via keystone-manage

Hi all, Keystone has deprecated the domain configuration upload capability provided through `keystone-manage`. We discussed it's removal in today's meeting [0] and wanted to send a quick note to the operator list. The ability to upload a domain config into keystone was done as a stop-gap until

[Openstack-operators] [telecom-nfv] Meeting #29

Hi All, Our next meeting is tomorrow, 15:00 UTC in #openstack-meeting-4. Thanks, Curtis. ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] [docs][all][ptl] Contributor Portal and Better New Contributor On-boarding

Hello all, Every month we have people asking on IRC or the dev mailing list having interest in working on OpenStack, and sometimes they're given different answers from people, or worse, no answer at all. Suggestion: lets work our efforts together to create some common documentation so that all

Re: [Openstack-operators] Leveraging Gnocchi in Mitaka

No worries, it makes me feel better to know I’m not doing something wrong. Thanks for all the assistance. On 6/27/17, 6:54 AM, "gordon chung" wrote: > > >On 26/06/17 06:07 PM, Tracy Comstock Roesler wrote: >> If I understand what you¹re saying, you think I can try >>

[Openstack-operators] [dev][doc] Operations Guide future

Thanks everyone for your feedback regarding the proposal below. Going forwards we are going to implement Option 3. If anyone is able to help out with this migration, please let me know :) Looking forward to getting started! From: Alexandra Settle Date: Thursday, June 1,

Re: [Openstack-operators] [User-committee] [openstack-dev] [all][tc] Turning TC/UC workgroups into OpenStack SIGs

Blair Bethwaite wrote: > There is a not insignificant degree of irony in the fact that this > conversation has splintered so that anyone only reading > openstack-operators and/or user-committee is missing 90% of the > picture Maybe I just need a new ML management strategy. That irony is not

Re: [Openstack-operators] [User-committee] [openstack-dev] [all][tc] Turning TC/UC workgroups into OpenStack SIGs

There is a not insignificant degree of irony in the fact that this conversation has splintered so that anyone only reading openstack-operators and/or user-committee is missing 90% of the picture Maybe I just need a new ML management strategy. I'd like to add a +1 to Sean's suggestion about

Re: [Openstack-operators] Leveraging Gnocchi in Mitaka

On 26/06/17 06:07 PM, Tracy Comstock Roesler wrote: > If I understand what you¹re saying, you think I can try > direct://?publisher=gnocchi in the pipeline.yaml on the controller nodes, > but not the compute nodes to bypass the collector? sorry, i just looked at the code again, it was only

Re: [Openstack-operators] OpenStack User Survey Now Open

Allison I clicked on "Add Deployment" and I got a 404 page (with a cat) The URL I was redirected to is: https://www.openstack.org/%7B$Controller.Link%7D%7B$CurrentStep.Template.Title%7D/add-entity Saverio 2017-06-26 23:44 GMT+02:00 Allison Price : > Hi everyone, > > If

Re: [Openstack-operators] [packaging][ubuntu] nova-api + nova-placement-api package conflict

Hi Chris On Tue, 27 Jun 2017 at 02:57 Chris Apsey wrote: > James, > > Bug report submitted. > Thanks (https://bugs.launchpad.net/cloud-archive/+bug/1700677 for reference here). Fix committed to package git repository; however we have some stable release updates