Re: [Openstack-operators] Forum Brainstorming???

Thanks Shamail - We’ve just completed a first pass on our brainstorming in the Scientific WG. Some ideas from a research computing perspective are here: https://etherpad.openstack.org/p/BOS-UC-brainstorming-scientific-wg More input from WG members (and anyone else) is of course welcome and a

Re: [Openstack-operators] Ansible OpenStack dnsmasq errors in syslog

Hi Lawrence, (Copying my response from the dev list! as a note, if you add [openstack-ansible] in the title it allows filters to filter it a bit better) Thanks for raising this. The 10.255.255.x range is used by lxcbr0 on the host, to assign the eth0 address to the containers. In essence this won'

Re: [Openstack-operators] [openstack] Unable to launch an instance

Thanks you all for your responses. Problem is resolved at my end with the help of folks in #openstack-ansible chat room. Problem was in my yml configuration file where a non-existent interface was specified. Regards, Amit On Wed, Mar 1, 2017 at 12:24 AM, Kris G. Lindgren wrote: > You should lo

[Openstack-operators] The OpenStack Summit is returning to Vancouver in May 2018

Hi everyone, Back by popular demand, the OpenStack Summit is returning to Vancouver , BC , BC from May 21-24, 2018. Registration, sponsorship

Re: [Openstack-operators] [User-committee] Forum Brainstorming???

I remember there was a discussion about having a session for all UC Working Group to meet together for collaboration and sharing works. Would this be a session submitted by UC? Also there was a previous discussion about improving the OpenStack Summit session/track selection process in the track-ch

[Openstack-operators] [Manila] v1 API removal

The v1 API for Manila has been deprecated for a long time and we plan to remove it in Pike. No users have come forward asking for v1 support to be continued, but in case any v1 users still exist, the transition plan is to use v2.0 instead. The v2 API has microversions and v2.0 is defined to be

[Openstack-operators] [keystone][defcore][refstack] Removal of the v2.0 API

During the PTG, Morgan mentioned that there was the possibility of keystone removing the v2.0 API [0]. This thread is a follow up from that discussion to make sure we loop in the right people and do everything by the books. The result of the session [1] listed the following work items: - Figure ou