Re: [Openstack-operators] [openstack-dev] [nova][glance] Who needs multiple api_servers?

I agree. I think the solution proposed earlier in this thread about making default to service catalog and optionally allow ops to choose 'the list of glance-apis to send data to', would make everyone's life easier. On Mon, May 1, 2017 at 2:16 PM, Blair Bethwaite

[Openstack-operators] [glance] glance developers and operators midcycle sync -- recordings

Hi all, We'd a midcycle sync last month with the glance development team and operators team where different individuals from across varied time zones participated. While the scheduling was a challenge and some had to join too early or too late, the event was pretty successful. We'd a ton of

[Openstack-operators] [glance] [glance_store] Removing the S3 driver

Hi all, Just wanted to follow up on the deprecation of S3 driver that Flavio started [1], we are now in the phase of removing the S3 driver from glance_store tree [2]. I've added some documentation to the release notes but have a feeling that operators may be using more than that to read up on

Re: [Openstack-operators] [openstack-dev] [glance] Proposal for a mid-cycle virtual sync on operator issues

/newton-glance-and-ops-midcycle-sync [2] http://www.timeanddate.com/worldclock/meetingdetails.html?year=2016=6=9=11=30=0=881=196=47=22=157=87=24=78=283=1800 [3] https://wiki.openstack.org/wiki/VirtualSprints#Glance_and_Operators_mid-cycle_sync_for_Newton Cheers On 5/31/16 5:13 PM, Nikhil Komawar wrote

Re: [Openstack-operators] [openstack-dev] [glance] Proposal for a mid-cycle virtual sync on operator issues

w > timeanddate suggestions is 6/7 of June. > > Belmiro > > On Tue, May 31, 2016 at 6:13 PM, Nikhil Komawar <nik.koma...@gmail.com > <mailto:nik.koma...@gmail.com>> wrote: > > Hey, > > > > > > Thanks for the feedback. 0800UTC is 4am EDT for some o

Re: [Openstack-operators] [openstack-dev] [glance] Proposal for a mid-cycle virtual sync on operator issues

Nikhil, > > 2000UTC might catch a few kiwis, but it's 6am everywhere on the east > coast of Australia, and even earlier out west. 0800UTC, on the other > hand, would be more sociable. > > On 26 May 2016 at 15:30, Nikhil Komawar <nik.koma...@gmail.com> wrote: >> Thanks

Re: [Openstack-operators] [openstack-dev] [glance] Proposal for a mid-cycle virtual sync on operator issues

, Nikhil Komawar wrote: > Thanks Sam. We purposefully chose that time to accommodate some of our > community members from the Pacific. I'm assuming it's just your case > that's not working out for that time? So, hopefully other Australian/NZ > friends can join. > > > On 5/26/16 1

Re: [Openstack-operators] [openstack-dev] [glance] Proposal for a mid-cycle virtual sync on operator issues

ple from the Large Deployment Team can come along. It’s > not a good time for me in Australia but hoping someone else can join in. > > Sam > > >> On 26 May 2016, at 2:16 AM, Nikhil Komawar <nik.koma...@gmail.com> wrote: >> >> Hello, >> >> >> F

[Openstack-operators] [openstack-dev] [glance] Proposal for a mid-cycle virtual sync on operator issues

[1] https://etherpad.openstack.org/p/newton-glance-and-ops-midcycle-sync -- Thanks, Nikhil Komawar Newton PTL for OpenStack Glance ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mai

Re: [Openstack-operators] [openstack-dev] [glance] glance-registry deprecation: Request for feedback

On 5/13/16 4:29 PM, Flavio Percoco wrote: > On 13/05/16 15:52 -0400, Nikhil Komawar wrote: >> >> >> On 5/13/16 3:36 PM, Flavio Percoco wrote: >>> On 12/05/16 21:41 -0400, Nikhil Komawar wrote: >>>> I have been of the same opinion as far as upgrades g

Re: [Openstack-operators] [openstack-dev] [glance] glance-registry deprecation: Request for feedback

On 5/13/16 3:36 PM, Flavio Percoco wrote: > On 12/05/16 21:41 -0400, Nikhil Komawar wrote: >> I have been of the same opinion as far as upgrades go. >> >> I think we are stepping ahead of ourselves here a bit. We need to >> figure out >> the rolling upgrad

Re: [Openstack-operators] [openstack-dev] [openstack-operators] [glance] Austin summit summary: Rolling upgrades

, Nikhil Komawar wrote: > Hello everyone, > > Just wanted to send a brief summary of the discussions at the summit. > This list is not holistic however, it covers the relevant aspects that > various stakeholders need to be aware of. > > * The intent is that we want operators

Re: [Openstack-operators] [openstack-dev] [glance] glance-registry deprecation: Request for feedback

I have been of the same opinion as far as upgrades go. I think we are stepping ahead of ourselves here a bit. We need to figure out the rolling upgrade story first and see if registry is actually useful or not there as well. The feedback from operator sessions also indicated that some ops do use

[Openstack-operators] [openstack-dev] [openstack-operators] [glance] Austin summit summary: Rolling upgrades

Hello everyone, Just wanted to send a brief summary of the discussions at the summit. This list is not holistic however, it covers the relevant aspects that various stakeholders need to be aware of. * The intent is that we want operators to be able to upgrade from one Glance release to the

Re: [Openstack-operators] [openstack-operators] [glance] [Austin summit] Glance session for operator feedback

NOTE: this is a operator focused session and has been tagged for ops for it to appear in cross track! On 4/20/16 1:39 PM, Nikhil Komawar wrote: > Hi all, > > At the Austin summit, I've scheduled a Glance work session [1] for > gathering input on Glance deployments and feedback

[Openstack-operators] [openstack-operators] [glance] [Austin summit] Glance session for operator feedback

to start threads after the summit when we have more feedback gathered. [1] https://www.openstack.org/summit/austin-2016/summit-schedule/events/9280?goback=1 [2] https://etherpad.openstack.org/p/newton-glance-operator-feedback -- Thanks, Nikhil Komawar Newton PTL for OpenStack Glance

Re: [Openstack-operators] [openstack-dev] [glance] Remove `run_tests.sh` and `tools/*`

this purpose? I am aware that some ops do prefer it. On 3/4/16 2:20 PM, Flavio Percoco wrote: > On 04/03/16 14:12 -0500, Nikhil Komawar wrote: >> Surely you can directly use the standard libraries to test systemwide >> but I am more curious to know if there are some who are still usi

Re: [Openstack-operators] [openstack-dev] [glance] Remove `run_tests.sh` and `tools/*`

Surely you can directly use the standard libraries to test systemwide but I am more curious to know if there are some who are still using run_tests wrappings that exist for to ease the pain a bit. On 3/4/16 12:41 PM, Flavio Percoco wrote: > On 04/03/16 11:59 -0500, Nikhil Komawar wrote: &

Re: [Openstack-operators] [openstack-dev] [glance] Remove `run_tests.sh` and `tools/*`

I think the hard question to me here is: Do people care about testing code on system installs vs. virtual env? run_tests does that and for some cases when you want to be extra sure about your CICD nodes, packaging and upgrades, the problem is solved. Are packagers using tox to this purpose? On

[Openstack-operators] Adding v1 LIKE support to python-glanceclient releases 1.x.x

Hi all, We recently release python-glanceclient 1.0.0 and it has the default shell version as v2. This may result into some scripts not detecting the change by default and discomfort to an extent. So, I am reaching out to this list with the hope of getting some feedback on the requirements, pros