from:"Nikhil Komawar"

Re: [openstack-dev] [glance] nominating Nikhil Komawar for glance core

2017-11-21 Thread Nikhil Komawar

Thank you all for the support. I intend to help the Glance community
flourish, again.

cheers

On Tue, Nov 21, 2017 at 10:07 AM, Brian Rosmaita <rosmaita.foss...@gmail.com
> wrote:

> Having heard only positive responses, I'm happy to reinstate Nikhil
> Komawar as a glance core, with all the rights and privileges
> pertaining thereto.
>
> Welcome back, Nikhil!
>
> cheers,
> brian
>
> On Thu, Nov 16, 2017 at 8:20 PM, Abhishek Kekane <akek...@redhat.com>
> wrote:
> > Big +2
> > Glad you are back :)
> >
> > Abhishek
> >
> > On 17-Nov-2017 4:59 AM, "Brian Rosmaita" <rosmaita.foss...@gmail.com>
> wrote:
> >>
> >> I'm sure I don't need to introduce Nikhil Komawar (nikhil in IRC), who
> >> was Glance PTL for the Kilo, Liberty, and Newton releases and who was
> >> a long time Glance core until he stepped down at the end of June this
> >> year.  Nikhil has informed me that he now has time to do Glance code
> >> reviews again, and I will be happy to have his experience and
> >> knowledge of the Glance code base available to inform our code
> >> reviews, and I propose to reinstate him as a member of the glance core
> >> team.
> >>
> >> I discussed this with the other cores present at today's weekly Glance
> >> meeting, and they support reinstating Nikhil, so I don't see any
> >> reason to have a long waiting period.  I'd like to add Nikhil to the
> >> core list on Monday, November 20, so if anyone has any comments or
> >> concerns, please let me know before then.
> >>
> >> thanks!
> >> brian
> >>
> >> 
> __
> >> OpenStack Development Mailing List (not for usage questions)
> >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
> unsubscribe
> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> >
> > 
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
> unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
>



-- 
--
Thanks,
Nikhil
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [glance] Does glance_store swift driver support range requests ?

2017-11-13 Thread Nikhil Komawar

I think it will a rather hard problem to solve. As swift store can be
configured to store objects in different configurations. I guess the next
question would be, what is your underlying problem -- multiple build
requests or is this for retry for a single download?

If the image is in image cache and you are hitting the glance node with
cached image (which is quite possible for tiny deployments), this feature
will be relatively easier.

On Mon, Nov 13, 2017 at 6:47 AM, Matt Keenan  wrote:

> Hi,
>
>  Just configured devstack on Fedora 26, and by default glance_store uses
> swift for image storage. When attempting to get a specific range from a
> glance stored image, it's reporting range requests are not supported e.g.:
>
> $ curl -i -X GET -r 0-32 -H "X-Auth-Token: $auth_token"
> http://10.169.104.255/image/v2/images/29b7aa
> 5e-3ec2-49b5-ab6b-d6cc5099f46c/file
> HTTP/1.1 400 Bad Request
> Date: Mon, 13 Nov 2017 10:43:23 GMT
> Server: Apache/2.4.27 (Fedora) OpenSSL/1.1.0f-fips mod_wsgi/4.5.15
> Python/2.7
> Content-Length: 205
> Content-Type: text/html; charset=UTF-8
> x-openstack-request-id: req-5ed2239f-165b-406f-969b-5cc4ab8c632d
> Connection: close
>
> 
>  
>   400 Bad Request
>  
>  
>   400 Bad Request
>   Getting images randomly from this store is not supported. Offset: 0,
> length: 33
>  
>
> Upon investigation, glance-api log is emitting:
>
> Nov 13 10:45:31 devstack@g-api.service[22783]: #033[01;31mERROR
> glance.location [#033[01;36mNone req-ad6da3f0-ead1-486a-a873-d301f02b0888
> #033[00;36mdemo demo#033[01;31m] 
> #033[01;35m#033[0│·1;31mGlance
> tried all active locations to get data for image
> 29b7aa5e-3ec2-49b5-ab6b-d6cc5099f46c but all have failed.#033[00m:
> StoreRandomGetNotSupported: Getting images randomly from this store is
> notMDg4OCAjMDMzWzAwOzM2bW supported. Offset: 0, length: 33
>
> The exception StoreRandomGetNotSupported is emitted by glance_store from
> glance_store/capabilities.py:
>
> op_exec_map = {
> 'get': (exceptions.StoreRandomGetNotSupported
> if kwargs.get('offset') or kwargs.get('chunk_size') else
> exceptions.StoreGetNotSupported),
> 'add': exceptions.StoreAddDisabled,
> 'delete': exceptions.StoreDeleteNotSupported}
>
> Looking at _driver/swift/store.py I think range requests are supported, it
> I've be unsuccessful in configuring it.
>
> Does the glance_store swift driver support range requests ?
>
> Can it be configured within a conf file, by somehow adding a capability ?
>
> thanks
>
> Matt
>
> --
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
--
Thanks,
Nikhil
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [glance] Image encryption

2017-11-10 Thread Nikhil Komawar

Hey,

the feature still exists. you may read about it more on
https://github.com/openstack/glance/blob/master/doc/source/user/signature.rst
,
https://specs.openstack.org/openstack/glance-specs/specs/liberty/image-signing-and-verification-support.html


for future references, please look/search at the specs for detailed
information/discussions http://specs.openstack.org/

On Thu, Nov 9, 2017 at 12:29 AM, Peng Liu  wrote:

> Hi,
>
> I've been looking at the bp[1], which used to be named 'Glance Image
> Signing and Encryption' at beginning. But encryption was remove after a
> meet-up according [2].
>
> Could anyone tell me 1) why the the image encryption was removed? 2) if it
> still makes sense for Glance to have such functionality?
>
>
> [1] https://blueprints.launchpad.net/glance/+spec/image-
> signing-and-verification-support
> [2] https://etherpad.openstack.org/p/liberty-glance-image-signing-and-
> encryption
>
>
> Thanks,
> --
> Peng Liu
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
--
Thanks,
Nikhil
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [glance] stepping down from glance core and other related groups

2017-06-28 Thread Nikhil Komawar

I am thankful to the community for such amazing experience over the past
few years. For the changes required for glance personnel in the active
cycle, I would like to step down from core as I cannot commit as much time
upstream. I was hanging out to help in general but even that time
commitment will be difficult in the coming months. This should effectively
mean, me stepping down from the release, core-sec, specs core groups too. I
am happy to help where needed on case by case basis but I do not think
+2/-2 rights or me being subscribed to glance-core-sec is needed for such.

Good luck to glancers and all those who form (ionic or covalent) bonds with
the glance community. Cheers.

-- 
--
Thanks,
Nikhil
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [glance] nominating Abhishek Kekane for glance core

2017-06-28 Thread Nikhil Komawar

This is a good move. I appreciate strong decisions as these are much needed
now.

On Fri, Jun 16, 2017 at 10:26 AM, Brian Rosmaita  wrote:

> I'm nominating Abhishek Kekane (abhishekk on IRC) to be a Glance core
> for the Pike cycle.  Abhishek has been around the Glance community for
> a long time and is familiar with the architecture and design patterns
> used in Glance and its related projects.  He's contributed code,
> triaged bugs, provided bugfixes, and done quality reviews for Glance.
>
> Abhishek has been proposed for Glance core before, but some members of
> the community were concerned that he wasn't able to devote sufficient
> time to Glance.  Given the current situation with the project,
> however, it would be an enormous help to have someone as knowledgeable
> about Glance as Abhishek to have +2 powers.  I discussed this with
> Abhishek, he's aware that some in the community have that concern, and
> he's agreed to be a core reviewer for the Pike cycle.  The community
> can revisit his status early in Queens.
>
> Now that I've written that down, that puts Abhishek in the same boat
> as all core reviewers, i.e., their levels of participation and
> commitment are assessed at the beginning of each cycle and adjustments
> made.
>
>

Although I am unsure about my commitment for Queens, in my current
situation I can no longer help with urgent reviews so I would like to step
down. A official email to follow.



> In any case, I'd like to put Abhishek to work as soon as possible!  So
> please reply to this message with comments or concerns before 23:59
> UTC on Monday 19 June.  I'd like to confirm Abhishek as a core on
> Tuesday 20 June.
>
> thanks,
> brian
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
--
Thanks,
Nikhil
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [glance] nominating Mike Fedosin for glance core

2017-05-25 Thread Nikhil Komawar

This is great news. Always +2 for Mike, he's been great (dev, glancer,
stacker ..) all the years.  Let's not wait so long for reinstatement if
folks are on-board, as having another core will only help.

On Thu, May 25, 2017 at 11:53 AM, Brian Rosmaita  wrote:

> As you've no doubt read elsewhere on the ML, we've lost several glance
> cores recently due to employment changes.  Luckily, Mike Fedosin
> informed me at today's Glance weekly meeting that he will have time
> for the next few months to devote some time to Glance reviewing.
>
> For those who don't know Mike (mfedosin on IRC), he was a Glance core
> for several years.  He provided a lot of notes that were used to write
> the Glance architecture documentation that is so helpful to new
> contributors, so he's extremely knowledgeable about the design
> patterns used in Glance.
>
> Most recently, Mike's been working on the Glare project, which has a
> lot in common with Glance.  While Mike says he can't commit much time
> to Glance development, he has proposed porting some of the Glare tests
> over to Glance, which will certainly help with our code coverage, and
> would be a helpful addition to Glance.
>
> (Mike agreed at today's Glance meeting not to propose re-integrating
> Glare into the Glance project until the Queens PTG (if at all), so I'm
> not worried about that being a distraction during the Pike cycle when
> we are so short-handed.)
>
> I'd like to reinstate Mike as a Glance core contributor at the next
> Glance weekly meeting.  Please reply to this message with any comments
> or concerns before 23:59 UTC on Wednesday 31 May 2017.
>
> cheers,
> brian
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
--
Thanks,
Nikhil
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Onboarding rooms postmortem, what did you do, what worked, lessons learned

2017-05-25 Thread Nikhil Komawar

Kendall, Thanks for that pointer and to those who sent emails. I guess the
pre-summit time was a bit weird this time around (for many cores/liaisons)
and may be the next round we will see someone from Glance participate.

Unfortunately, I can't be a Glance liaison at the moment. I hope someone
will be more willing to step up.

Thanks again for making this effort easier for the entire community.

Cheers

On Wed, May 24, 2017 at 6:20 PM, Kendall Nelson <kennelso...@gmail.com>
wrote:

> @Nikhil, we (the organizers of Upstream Institute) sent a few emails
> [1][2] out to the dev mailing list asking for help and representatives from
> various projects to attend and get involved. We are also working on
> building a network of project liaisons to direct newcomers to in each
> project. Would you be interested in being our Glance liaison?
>
> Let me know if you have any other Upstream Institute questions!
>
> - Kendall(diablo_rojo)
>
> [1] http://lists.openstack.org/pipermail/openstack-dev/2017-
> January/110788.html
> [2]  http://lists.openstack.org/pipermail/openstack-dev/2016-
> November/108084.html
>
> On Wed, May 24, 2017 at 4:03 PM Nikhil Komawar <nik.koma...@gmail.com>
> wrote:
>
>> Project:  Glance
>>
>> Attendees: ~15
>>
>> What was done:
>>
>> We started by introducing the core team (or whatever existed then), did a
>> run down of Glance API documentation especially for developers, other
>> references like notes for ops, best practices. We went through the
>> architecture of the project. A few were interested in knowing more details
>> and going in depth so we discussed the design patterns that exist today,
>> scope of improvements and any blackholes therein, auxiliary services and
>> performance tradeoffs etc. A lot of the discussion was free form so people
>> asked questions and session was interactive.
>>
>>
>> What worked:
>>
>> 1. The projector worked!
>>
>> 2. Session was free form, there was good turnout and it was interactive.
>> (all the good things)
>>
>> 3. People were serious about contributing as per their
>> availability/capacity to do upstream and one person showed up asking to do
>> reviews.
>>
>>
>> Lessons:
>>
>> 1. Could have been advertised more at least the session description more
>> customized.
>>
>> 2. A representative from the team could have been officially invited to
>> the upstream institute training.
>>
>> 3. The community building sessions and on-boarding sessions seem to
>> overlap a bit so a representative from the team could be help in those
>> sessions for Q or more interaction. Probably more collaboration/prep
>> before the summit for such things. ($0.02)
>>
>>
>> Cheers
>>
>> On Wed, May 24, 2017 at 1:27 PM, Jay S Bryant <jungleb...@gmail.com>
>> wrote:
>>
>>> Project:  Cinder
>>>
>>> Attendees: Approximately 30
>>>
>>> I was really pleased by the number of people that attended the Cinder
>>> session and the fact that they people in the room seemed engaged with the
>>> presentation and asked good questions showing interest in the project.  I
>>> think having the on-boardings rooms was beneficial and hopefully something
>>> that we can continue.
>>>
>>> Given the number of people in the room we didn't go around and introduce
>>> everyone.  I did have the Sean McGinnis introduce himself as PTL and had
>>> the other Cinder Core members introduce themselves so that the attendees
>>> could put faces with our names.
>>>
>>> From there we kicked off the presentation [1] which covered the
>>> following high level topics:
>>>
>>>- Introduction of Cinder's Repos and components
>>>- Quick overview of Cinder's architecture/organization
>>>- Pointers to the Upstream Institute education (Might have done a
>>>bit of a sales pitch for the next session here ;-))
>>>- Expanded upon the Upstream Institute education to explain how what
>>>was taught there specifically applied to Cinder
>>>- Walked through the main Cinder code tree
>>>- Described how to test changes to Cinder
>>>
>>> My presentation was designed to assume that attendees had been through
>>> Upstream Institute.  I had coverage in the slides in case they had not been
>>> through the education.  Unfortunately most of the class had not been
>>> through the education so I did spend a portion of time re-iterating those
>>> concepts and less time was able to be spent

Re: [openstack-dev] [glance] Stepping Down

2017-05-24 Thread Nikhil Komawar

Dharini,

Thanks for your good work. It's been good working with you on Glance. All
the best!

Cheers

On Mon, May 22, 2017 at 8:46 PM, Chandrasekar, Dharini <
dharini.chandrase...@intel.com> wrote:

> Hello Glancers,
>
>
>
> Due to a change in my job role with my employer, I unfortunately do not
> have the bandwidth to contribute to Glance in the capacity of a Core
> Contributor.
>
> I hence would have to step down from my role of a Core Contibutor in
> Glance.
>
>
>
> I had a great experience working in OpenStack Glance. Thank you all for
> your help and support. I wish you all, good luck in all your endeavors.
>
>
>
> Thanks,
>
> Dharini.
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
--
Thanks,
Nikhil
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [glance] Stepping Down

2017-05-24 Thread Nikhil Komawar

Hemanth, sorry to see you step down here. Thanks for your astute input all
along. All the best!

Cheers

On Fri, May 19, 2017 at 5:49 PM, Hemanth Makkapati 
wrote:

> Glancers,
> Due to a significant change to my job description, I wouldn't be able to
> contribute to Glance in the capacity of a core reviewer going forward.
> Hence, I'd like to step down from my role immediately.
> For the same reason, I'd like to step down from Glance coresec and release
> liaison roles as well.
>
> Thanks for all the help!
>
> Rooting for Glance to do great things,
> Hemanth Makkapati
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
--
Thanks,
Nikhil
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [glance][openstack-ansible] Moving on

2017-05-24 Thread Nikhil Komawar

Sorry to see you go, Steve. Your code, feedback and all the work has always
been super helpful so thank you very much. You shall be an asset to any
team you work on. All the best!

On Thu, May 18, 2017 at 11:55 PM, Steve Lewis  wrote:

> It is clear to me now that I won't be able to work on OpenStack as a part
> of my next day job, wherever that ends up being. As such, I’ll no longer be
> able to invest the time and energy required to maintain my involvement in
> the community. It's time to resign my role as a core reviewer, effective
> immediately.
>
> Thanks for all the fish.
> --
> SteveL
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
--
Thanks,
Nikhil
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Onboarding rooms postmortem, what did you do, what worked, lessons learned

2017-05-24 Thread Nikhil Komawar

Project:  Glance

Attendees: ~15

What was done:

We started by introducing the core team (or whatever existed then), did a
run down of Glance API documentation especially for developers, other
references like notes for ops, best practices. We went through the
architecture of the project. A few were interested in knowing more details
and going in depth so we discussed the design patterns that exist today,
scope of improvements and any blackholes therein, auxiliary services and
performance tradeoffs etc. A lot of the discussion was free form so people
asked questions and session was interactive.


What worked:

1. The projector worked!

2. Session was free form, there was good turnout and it was interactive.
(all the good things)

3. People were serious about contributing as per their
availability/capacity to do upstream and one person showed up asking to do
reviews.


Lessons:

1. Could have been advertised more at least the session description more
customized.

2. A representative from the team could have been officially invited to the
upstream institute training.

3. The community building sessions and on-boarding sessions seem to overlap
a bit so a representative from the team could be help in those sessions for
Q or more interaction. Probably more collaboration/prep before the summit
for such things. ($0.02)


Cheers

On Wed, May 24, 2017 at 1:27 PM, Jay S Bryant  wrote:

> Project:  Cinder
>
> Attendees: Approximately 30
>
> I was really pleased by the number of people that attended the Cinder
> session and the fact that they people in the room seemed engaged with the
> presentation and asked good questions showing interest in the project.  I
> think having the on-boardings rooms was beneficial and hopefully something
> that we can continue.
>
> Given the number of people in the room we didn't go around and introduce
> everyone.  I did have the Sean McGinnis introduce himself as PTL and had
> the other Cinder Core members introduce themselves so that the attendees
> could put faces with our names.
>
> From there we kicked off the presentation [1] which covered the following
> high level topics:
>
>- Introduction of Cinder's Repos and components
>- Quick overview of Cinder's architecture/organization
>- Pointers to the Upstream Institute education (Might have done a bit
>of a sales pitch for the next session here ;-))
>- Expanded upon the Upstream Institute education to explain how what
>was taught there specifically applied to Cinder
>- Walked through the main Cinder code tree
>- Described how to test changes to Cinder
>
> My presentation was designed to assume that attendees had been through
> Upstream Institute.  I had coverage in the slides in case they had not been
> through the education.  Unfortunately most of the class had not been
> through the education so I did spend a portion of time re-iterating those
> concepts and less time was able to be spent at the end going through real
> world examples of working with changes in Cinder.  I got feedback from a
> few people that having some real hands on coding examples would have been
> helpful.
>
> One way we could possible handle this is to split the on-boarding to a
> introduction section and then a more advanced second session.  The other
> option is that we require people who are attending the on-boarding to have
> been through Upstream Institute.  Something to think about.
>
> I think it was unfortunate that the session wasn't recorded.  We shared a
> lot of good information (between good questions and having a good
> representation of Cinder's Core team in the room) that it would have been
> nice to capture.  Given this I am planning at some point in the near future
> to work with Walt Boring to record a version of the presentation that can
> be uploaded to our Cinder YouTube channel and include some coding examples.
>
> In summary, I think the on-boarding rooms were a great addition and the
> Cinder team is pleased with how we used the time.  I think it is something
> we would like to continue to invest time into developing and improving.
>
> Jay
>
> [1] https://www.slideshare.net/JayBryant2/openstack-cinder-
> onboarding-education-boston-summit-2017
>
>
> On 5/19/2017 3:43 PM, Lance Bragstad wrote:
>
> Project: Keystone
> Attendees: 12 - 15
>
> We conflicted with one of the Baremetal/VM sessions
>
> I attempted to document most of the session in my recap [0].
>
> We started out by doing a round-the-room of introductions so that folks
> could put IRC nicks to faces (we also didn't have a packed room so this
> went pretty quick). After that we cruised through a summary of keystone,
> the format of the projects, and the various processes we use. All of this
> took *maybe* 30 minutes.
>
> From there we had an open discussion and things evolved organically. We
> ended up going through:
>
>- the differences between the v2.0 and v3 APIs
>- keystonemiddleware architecture, how it aids

Re: [openstack-dev] [glance] please approve test patch to fix glanceclient

2017-05-24 Thread Nikhil Komawar

thanks (for your work and to Flavio for the other +2). this is done as well.

On Wed, May 24, 2017 at 1:07 PM, Eric Fried <openst...@fried.cc> wrote:

> Thanks Nikhil.  This one is also needed to make py35 pass:
>
> https://review.openstack.org/#/c/396816/
>
> E
>
> On 05/24/2017 10:55 AM, Nikhil Komawar wrote:
> > thanks for bringing it up. this is done.
> >
> > On Wed, May 24, 2017 at 10:54 AM, Sean Dague <s...@dague.net
> > <mailto:s...@dague.net>> wrote:
> >
> > python-glanceclient patches have been failing for at least a week
> due to
> > a requests change. The fix was posted 5 days ago -
> > https://review.openstack.org/#/c/466385
> > <https://review.openstack.org/#/c/466385>
> >
> > It would be nice to get that approved so that other patches could be
> > considered.
> >
> > -Sean
> >
> > --
> > Sean Dague
> > http://dague.net
> >
> > 
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > <http://openstack-dev-requ...@lists.openstack.org?subject:
> unsubscribe>
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
> >
> >
> >
> >
> > 
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:
> unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
--
Thanks,
Nikhil
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [glance] please approve test patch to fix glanceclient

2017-05-24 Thread Nikhil Komawar

thanks for bringing it up. this is done.

On Wed, May 24, 2017 at 10:54 AM, Sean Dague  wrote:

> python-glanceclient patches have been failing for at least a week due to
> a requests change. The fix was posted 5 days ago -
> https://review.openstack.org/#/c/466385
>
> It would be nice to get that approved so that other patches could be
> considered.
>
> -Sean
>
> --
> Sean Dague
> http://dague.net
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Disabling glance v1 by default in devstack

2017-03-07 Thread Nikhil Komawar

Thanks Matt. Yes please, lets all start getting rid of glance v1 in our
tests and then on..

On 3/3/17 2:35 PM, Matt Riedemann wrote:
> I've got a change proposed to disable glance v1 by default in devstack
> for Pike [1].
>
> The glance v1 API has been deprecated for awhile now. Nova started
> supporting glance v2 in Newton and removed the ability to use nova
> with glance v1 in Ocata.
>
> It also turns out that Tempest will do things with glance v1 over v2
> during test setup of glance v1 is available, so we're missing out on
> some v2 coverage.
>
> The time has come to change the default. If you have a project or CI
> jobs that require glance v1, first, you should probably start moving
> to v2, and second, you can re-enable this by setting
> GLANCE_V1_ENABLED=True in the settings/localrc for your devstack plugin.
>
> [1] https://review.openstack.org/#/c/343129/
>

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] artifacts code removed from the glance codebase in Pike

2017-02-20 Thread Nikhil Komawar

Great move. Let's get this merged asap.

Thanks!

best,
-Nikhil

On Thu, Feb 16, 2017 at 11:15 PM, Brian Rosmaita  wrote:

> If you've never deployed, packaged, or used the Artifacts API supplied
> by Glance or Glare, you can safely disregard this message.
>
> There's a patch up [0] to remove the legacy EXPERIMENTAL Artifacts API
> code from the Glance code repository.  (This is an entirely separate
> issue from the question of whether the Glare *project* should be
> independent or part of Glance, which we'll be discussing at the PTG next
> week [1].)  I would like the patch to merge as soon as possible, but I
> also wanted to give people a heads-up in case anyone would be impacted
> by this change.
>
> The situation is explained in detail in the releasenotes [2] included on
> the patch.  Please let me know immediately if there is a reason why we
> should hold off merging this patch.  Otherwise, I'd like to merge it
> before the post-PTG burst of code changes begins.
>
> thanks,
> brian
>
> [0] https://review.openstack.org/427535
> [1] "Macon" room, 9:30-10:30 on Thursday
> [2]
> https://review.openstack.org/#/c/427535/14/releasenotes/
> notes/glare-ectomy-72a1f80f306f2e3b.yaml
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [glance] user survey question results

2017-02-20 Thread Nikhil Komawar

This info is excellent. Exactly the kind of context we need to get the
discussion on import refactor rolling.

best,
-Nikhil

On Mon, Feb 20, 2017 at 3:56 PM, Brian Rosmaita 
wrote:

> The responses to the Glance user survey question are in the following
> etherpad to make it easy to record reactions and/or suggestions for
> follow-up:
>
> https://etherpad.openstack.org/p/glance-user-survey-q-feb-2017
>
> This was the question we asked:
>
> "As you're aware, the Images API v1 supplied by OpenStack Glance is
> currently deprecated. If you haven't yet moved to the Images API v2,
> what is preventing you? Please be specific."
>
> cheers,
> brian
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [glance] revising the core list

2017-02-17 Thread Nikhil Komawar

Brian, thanks for revamping the rotation. I don't have any comments on
specific cores and their inactivity but I like the idea of we checking up
on the activeness of the glance community in a regular manner.

:thumbsup:

On Fri, Feb 17, 2017 at 11:19 AM, Brian Rosmaita <rosmaita.foss...@gmail.com
> wrote:

> Following Doug's suggestion in [0], I'm revising the Glance core list
> before next week's PTG.
>
> First, I'd again like to thank the following former Glance cores, who
> stepped down during the Ocata cycle, for their past service to Glance:
> - Sabari Murugesan
> - Stuart McLaren
>
> Second, I'd like to mention two people who were added to the Glance core
> team in Ocata, both of whom have made great contributions during the cycle:
> - Dharini Chandrasekar
> - Steve Lewis
>
> Third, I'd like to thank the Glance cores who continued to serve during
> the Ocata cycle:
> - Erno Kuvaja
> - Fei Long Wang
> - Flavio Percoco
> - Hemanth Makkapati
> - Ian Cordasco
> - Nikhil Komawar
>
> Finally, the following people are dropped from the Glance core list due
> to inactivity during Ocata.  On behalf of the entire Glance team, I
> thank each of you for your past service to Glance, and hope to see you
> again as Glance contributors:
> - Kairat Kushaev
> - Mike Fedosin
> - Louis Taylor
>
> This will leave some openings for new core contributors during the Pike
> cycle.  If you're interested in getting some advice about how to
> position yourself to become a Glance core, please seek out the active
> cores listed above during the PTG.  For people who won't be at the PTG,
> you can always look for active cores in #openstack-glance.
>
> Let's have a productive PTG!
>
> cheers,
> brian
>
> [0]
> http://lists.openstack.org/pipermail/openstack-dev/2017-
> February/112407.html
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Glance rolling upgrades database strategy implementation

2017-02-09 Thread Nikhil Komawar

Dmitry, thanks for your interest and appreciate your enthusiasm to work
on it. We've a few folks who are actively contributing to the same and
were able to release significant work, though experimental, in Ocata.
Please join the team on #openstack-glance or show up at one of our
meetings, reach out to the author of the spec, etc. whenever you plan to
pick up critical work.

P.S. Please note there's a sub-section on "Assignee" to the work and
well written on this spec. I encourage all spec proposes to indicate the
same so as to avoid confusions.

Best,

On 2/9/17 9:44 AM, Dmitry Stepanenko wrote:
> Hi,
>
> I'm going to work on implementation
> of 
> https://specs.openstack.org/openstack/glance-specs/specs/ocata/approved/glance/database-strategy-for-rolling-upgrades.html.
>
> If someone going to also work on this, have any concerns with my role
> in implementing this blueprint or gonna help me with it, feel free to
> get in touch with me.
>
> Kind regards,
> Dmitry
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-- 

Thanks,
Nikhil

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [glance] Propose Dharini Chandrasekar for Glance core

2017-01-24 Thread Nikhil Komawar

+1

She does good work and I will be happy to see this happen.

I am not so sure about the argument part :) (jk)


On 1/24/17 8:36 AM, Brian Rosmaita wrote:
> I'd like to propose Dharini Chandrasekar (dharinic on IRC) for Glance
> core.  She has been an active reviewer and contributor to the Glance
> project during the Newton and Ocata cycles, has contributed to other
> OpenStack projects, and has represented Glance in some interactions with
> other project teams.  Additionally, she recently jumped in and saw
> through to completion a high priority feature for Newton when the
> original developer was unable to continue working on it.  Plus, she's
> willing to argue with me (and the other cores) about points of software
> engineering.  She will be a great addition to the Glance core reviewers
> team.
>
> If you have any concerns, please let me know.  I plan to add Dharini to
> the core list after this week's Glance meeting.
>
> thanks,
> brian
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all][elections][TC] TC Candidacy

2016-09-28 Thread Nikhil Komawar

I noticed a good statement, marked it inline.


On 9/28/16 7:24 AM, John Davidge wrote:
> Hi Zane,
>
> Thanks for pointing this out! My interpretation of the StackForge
> Retirement page[1] was wrong on that point. I've updated the blog post to
> reflect that (without removing the original interpretation).
>
> The discussion about renaming git repos is a bit of a red herring, because
> what we're really talking about is what it *means* to be in Stackforge vs.
> OpenStack vs. OpenStack Family, not which git namespace a project should
> live in. Apologies if I didn't make that clear.
>
> Like many of us, I do my best to keep up with historical context, but when
> there is so much contradictory information/opinion out there about what
> OpenStack is/isn't was/wasn't it can be a struggle at times. The crux of

"""
> my proposal is aiming to solve that by not trying to be everything to
> everyone under one tent - by defining sensible boundaries to separate the
> different goals of the community.
"""

+1000 to sensible boundaries. the key factor is to strike the balance.
>
> All the best,
>
> John
>
> [1] https://wiki.openstack.org/wiki/Stackforge_Namespace_Retirement
>
> On 9/27/16, 5:13 PM, Zane Bitter wrote:
>
>> On 27/09/16 06:19, John Davidge wrote:
 Having Stackforge as a separate Github organization and set of
> repositories was a maintenance nightmare due to the awkwardness of
> renaming projects when they "moved into OpenStack".
>>> There's no reason that this would need a separate github structure, just
>>> separate messaging and rules.
>> That's exactly what we have now.
>>
>> This statement on your blog:
>>
>> "[StackForge] was retired in October 2015, at which point all projects
>> had to move into the OpenStack Big Tent or leave entirely."
>>
>> is completely false. That never happened. There are still plenty of
>> repos on git.openstack.org that are not part of the Big Tent. At no time
>> has any project been required to join the Big Tent in order to continue
>> being hosted.
>>
>> Maybe you should consider reading up on the historical background to
>> these changes. There are a lot of constraints that have to be met - from
>> technical ones like the fact that it's not feasible to rename git repos
>> when they move into or out of the official OpenStack project, to legal
>> ones like how the TC has to designate projects in order to trigger
>> certain rights and responsibilities in the (effectively immutable)
>> Foundation by-laws. Rehashing all of the same old discussions without
>> reference to these constraints is unlikely to be productive.
>>
>> cheers,
>> Zane.
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> 
> Rackspace Limited is a company registered in England & Wales (company 
> registered number 03897010) whose registered office is at 5 Millington Road, 
> Hyde Park Hayes, Middlesex UB3 4AZ. Rackspace Limited privacy policy can be 
> viewed at www.rackspace.co.uk/legal/privacy-policy - This e-mail message may 
> contain confidential or privileged information intended for the recipient. 
> Any dissemination, distribution or copying of the enclosed material is 
> prohibited. If you receive this transmission in error, please notify us 
> immediately by e-mail at ab...@rackspace.com and delete the original message. 
> Your cooperation is appreciated.
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [glance] newton rc-2 deadline

2016-09-26 Thread Nikhil Komawar

Added notes:

For all the bugs that are identified likely candidates need to be tagged
*newton-rc-potential*.

This tag has been added to the official glance bug tags list and can
also be used as a filter to view all of the potential rc bugs.

References:
https://bugs.launchpad.net/glance/+bugs?field.tag=newton-rc-potential
http://lists.openstack.org/pipermail/openstack-dev/2016-September/103827.html

On 9/23/16 4:05 PM, Brian Rosmaita wrote:
> We're going to need to cut rc-2 for Glance to accommodate some new
> translations, so there is an opportunity to include some conservative
> bugfixes.  Any such must be merged before 16:00 UTC on Wed 28 Sept, so I
> am setting a deadline of 12:00 UTC on Tue 27 Sept for approval.  If you
> have a bugfix that is a worthy candidate, please reply to this email with
> the appropriate info.
>
> cheers,
> brian
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 

Thanks,
Nikhil



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Glance] Cores using -2 votes

2016-09-23 Thread Nikhil Komawar

I empathize with you Erno. I think this is a case of sheer
mis-understanding and probably (I think) the mention of that instance /
situation in this email is only for referential purposes.


There are some critical deadlines one sub-set of people have to met and
there are other priorities other sub-set have. Co-ordination across
continents and low bandwidth conversations that do not necessarily
communicate the /intent/ every time results into such situations.


Let's /all/ move on and not regress on it. We do need improvement in the
process for /sure/ and I've already communicated my intentions with
rosmaita about them. You can expect something later next week as time
permits.



On 9/23/16 12:30 PM, Erno Kuvaja wrote:
> On Fri, Sep 23, 2016 at 3:42 PM, Ian Cordasco  wrote:
>> Hi all,
>>
>> A few weeks ago, there was a controversy in which a patch had been
>> -2'd until other concerns were resolved and then the core who used
>> their -2 powers disappeared and could not lift it after those concerns
>> had been resolved. This lead to a situation where the -2'd patch was
>> abandoned and then resubmitted with a new Change-Id so it could be
>> approved in time for a milestone.
>>
>> In chatting with some folks, it's become apparent that all of us
>> Glance cores need to keep a dashboard around of items that we've -2'd.
>>
>> The basic form of that is:
>>
>> https://review.openstack.org/#/q/reviewer:self+AND+label:code-review-2+AND+(project:openstack/glance+OR+project:openstack/glance_store+OR+project:openstack/python-glanceclient)
>>
>> Or the query in particular is:
>>
>> reviewer:self AND label:code-review-2 AND
>> (project:openstack/glance OR project:openstack/glance_store OR
>> project:openstack/python-glanceclient)
>>
>> That said, this will show any patch you have reviewed that has a -2 on
>> it. (This also ignores specs.)
>>
>> To find what *you* have -2'd, the query is a little bit different:
>>
>> label:code-review-2, AND
>> (project:openstack/glance OR project:openstack/glance_store OR
>> project:openstack/python-glanceclient)
>>
>> For example,
>>
>> label:code-review-2,sigmavirus24 AND (project:openstack/glance OR
>> project:openstack/glance_store OR
>> project:openstack/python-glanceclient)
>>
>> is my query.
>>
>> I think we would all appreciate it if as cores we could keep an eye on
>> our own -2's and keep them up-to-date.
>>
>> I suspect people here will want to ignore anything that was abandoned
>> so you can also do:
>>
>> label:code-review-2, AND -status:abandoned AND
>> (project:openstack/glance OR project:openstack/glance_store OR
>> project:openstack/python-glanceclient)
>>
>> Finally, if you use Gertty, you can use this query to do the same thing:
>>
>> label:Code-Review=-2, AND -status:abandoned AND
>> project:^openstack/.*glance.*
>>
>> Cheers,
>> --
>> Ian Cordasco
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> Ok, as it's becoming clear that the one wrong assumption did not slip
> from people (as I originally did not want to point it out), lets
> clarify this.
>
> There is difference between "not being able to" as referred in the
> original mailchain and "not willing to before verifying as the issues
> were flagged and their corrections slipped under radar long time
> before". I actually followed up that situation daily basis and got
> online on my holidays to make sure those -2s were not left hanging
> there without reason. That was the cause of the frustration and
> initial e-mail. Yes, it's important to track -2s, it's equally
> important to not assume it's not relevant just because you happen to
> think someone has addressed the reason for it.
>
> No bad feelings,
> Erno "jokke" Kuvaja
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 

Thanks,
Nikhil



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Glance] Cores using -2 votes

2016-09-23 Thread Nikhil Komawar

thanks Ian, this is great info.

Just a side question, do you have example for -Workflow , say in cases
when I'd +2ed but to keep a check on process and approve after the
freeze -W'ed it?

Nonetheless, I have been using the labels and owner/reviewer/project
field to good advantage so would like to acknowledge what you have to
say -- again, this is very effective and I will too encourage folks to
use such a bookmark.

If you need more options for querying, please read up the gerrit docs
https://review.openstack.org/Documentation/user-search.html

On 9/23/16 10:42 AM, Ian Cordasco wrote:
> Hi all,
>
> A few weeks ago, there was a controversy in which a patch had been
> -2'd until other concerns were resolved and then the core who used
> their -2 powers disappeared and could not lift it after those concerns
> had been resolved. This lead to a situation where the -2'd patch was
> abandoned and then resubmitted with a new Change-Id so it could be
> approved in time for a milestone.
>
> In chatting with some folks, it's become apparent that all of us
> Glance cores need to keep a dashboard around of items that we've -2'd.
>
> The basic form of that is:
>
> https://review.openstack.org/#/q/reviewer:self+AND+label:code-review-2+AND+(project:openstack/glance+OR+project:openstack/glance_store+OR+project:openstack/python-glanceclient)
>
> Or the query in particular is:
>
> reviewer:self AND label:code-review-2 AND
> (project:openstack/glance OR project:openstack/glance_store OR
> project:openstack/python-glanceclient)
>
> That said, this will show any patch you have reviewed that has a -2 on
> it. (This also ignores specs.)
>
> To find what *you* have -2'd, the query is a little bit different:
>
> label:code-review-2, AND
> (project:openstack/glance OR project:openstack/glance_store OR
> project:openstack/python-glanceclient)
>
> For example,
>
> label:code-review-2,sigmavirus24 AND (project:openstack/glance OR
> project:openstack/glance_store OR
> project:openstack/python-glanceclient)
>
> is my query.
>
> I think we would all appreciate it if as cores we could keep an eye on
> our own -2's and keep them up-to-date.
>
> I suspect people here will want to ignore anything that was abandoned
> so you can also do:
>
> label:code-review-2, AND -status:abandoned AND
> (project:openstack/glance OR project:openstack/glance_store OR
> project:openstack/python-glanceclient)
>
> Finally, if you use Gertty, you can use this query to do the same thing:
>
> label:Code-Review=-2, AND -status:abandoned AND
> project:^openstack/.*glance.*
>
> Cheers,
> --
> Ian Cordasco
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [release][congress][searchlight] projects in danger of being left out of newton

2016-09-19 Thread Nikhil Komawar

I think searchlight went right ahead into 1.0.0 so, I doubt if we will
have rc1. (this is just initial info, I will defer the details to the
project lead).



On 9/19/16 9:55 AM, Doug Hellmann wrote:
> We have not had RC1 tags for congress or searchlight, and the project
> leads aren't responding on IRC. These projects are at risk of being
> left out of the newton release. Someone from the core teams for
> these projects should get in touch with the release team as soon
> as possible to let us know your plans.
>
> Doug
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [release][requirements] fixing contraints urls in stable/newton

2016-09-16 Thread Nikhil Komawar

Hi,


There are many reviews pending on Glance's side for the u-c updates [1,
2, 3] given the u-c file for stable/newton doesn't exist yet [4].


However, I have observed that many reviews for u-c have been merged [5].
The former email in this thread says that merge is expected after the
requirements repo is branched.


What's the process around this and validation in process?


[1] https://review.openstack.org/#/c/371322/

[2] https://review.openstack.org/#/c/365731/

[3] https://review.openstack.org/365734

[4]
https://git.openstack.org/cgit/openstack/requirements/plain/upper-constraints.txt?h=stable/newton

[5] https://review.openstack.org/#/q/topic:create-newton



On 9/2/16 5:19 PM, Doug Hellmann wrote:
> We've discovered that the branching script had an overly restrictive
> regex for detecting the URL to the upper contraints file, so some
> repositories that have been branched and that use constraints did not
> receive the update to use the version of the constraints in the
> requirements stable branch.
>
> You'll need to manually create a patch to append "?h=stable/newton"
> to the end of the URL in your tox.ini files in your stable/newton
> branches.
>
> That said, we have not branched the requirements repository, yet, so the
> new URL won't work. We will announce when we've branched the
> requirements repository, so if you want to set up the patch and have it
> ready you will be able to land it quickly after the branch is ready.
>
> Doug
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 

Thanks,
Nikhil



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [glance] Glance stable/newton cut and ready for Ocata; lift your -2s/-Ws

2016-09-16 Thread Nikhil Komawar

Hi team,


Glance Newton rc1 is available, if you did not get a chance [1]. This
also means that all further Newton specific fixes need to first merge in
master and then backported to stable/newton branch (only stable maint
team has core rights on that branch [2]). The master branch is open for
Ocata development including new features, doc fixes, string fixes, etc.


So, those who haven't already please make it a point to lift up your
(cores') -2s/-Ws [3] blocks on the reviews you've helped stopped during
the Newton-3, RC1 phase or any Newton phase for that matter. This is the
time we need to start evaluating the potential of those reviews for
Ocata cycle.


Please NOTE: If an important (for those concerned) bug/feature is being
asked to move ahead and if the -2/-W by cores are not lifted up by
*EOD-September-19th*, we may encourage the developers to abandon that
review and propose an alternate one. And for all other reviews with
-2/-W by core(s) & are not abandoned, we will wait until
*EOD-September-30th* after which either they will be either abandoned or
the developer will be asked to propose alternative if -2/-W is not
lifted.  So, if you think that your -2/-W still counts (irrespective of
your earlier comment), please comment elaborately *again* on that review
so that everyone can be aware of your stance and help better resolve the
situation for everyone involved.


Thank you for your cooperation.


[1]
http://lists.openstack.org/pipermail/openstack-dev/2016-September/103827.html

[2] https://review.openstack.org/#/admin/groups/535,members

[3] In some cases, cores have chosen to -W instead of a -2 to block that
patch until a specific release date. This is to help review the patch
and indicate if it's okay to move forward after the release date i.e. a
core may give a +2 to indicate that the patch is technically okay but -W
it, to wait process wise. The block is interpretation based on cores'
opinions so let's not have more opinions/process on how /you/ think the
block should be.

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [glance] [elections] Glance PTL non-candidacy

2016-09-13 Thread Nikhil Komawar

Thanks wangxiyuan! I'm happy to work with you and truly appreciate all
your good work in Glance. Very glad to hear that my reviews are helping you.


On 9/13/16 4:29 AM, 王玺源 wrote:
> Hi Nikhil,
>
> You are the first PTL I knew when I started to work with OpenStack
> community, we can see your hard work for Glance during these cycles. I
> have learned a lot from your review suggestion. Thanks very much!!! 
> And it's great to know that you still work on Glance.  Best wishes.
>
> 2016-09-13 13:33 GMT+08:00 Nikhil Komawar <nik.koma...@gmail.com
> <mailto:nik.koma...@gmail.com>>:
>
> Thank you Fei Long. It's always a pleasure working with you!
>
>
>
>
>
> On 9/13/16 12:59 AM, Fei Long Wang wrote:
>
> > Hi Nikhil,
>
> >
>
> > Thanks for your hard work as Glance PTL, you did a great job. And
>
> > happy to know you will still work in OpenStack, see you around ;)
>
> >
>
> > On 12/09/16 18:08, Nikhil Komawar wrote:
>
> >> Hi team,
>
> >>
>
> >>
>
> >> Just wanted to share my decision for not running for PTL for
> Glance.
>
> >> It's been great serving the community in this role however,
> there are
>
> >> some personal and family matters that I need to attend to over
> the next
>
> >> couple of months or so.
>
> >>
>
> >>
>
> >> I think the Glance team has done great and we've quite a bunch
> of bright
>
> >> developers who are helping push the project forward in the
> appropriate
>
> >> direction. With Glare becoming separate project and Ocata being
> short
>
> >> cycle, I anticipate the priorities being rather obvious to
> those who
>
> >> have stayed in touch. I will be available to do the rightful
> handoff to
>
> >> the incoming PTL (for Ocata) and update with Newton happenings once
>
> >> we're done with a few important bugs that are being targeted
> for RC1.
>
> >>
>
> >>
>
> >> I intend to stick around in Glance and related projects like
>
> >> Searchlight, Glare, etc. However, I am planning to take a more
> hands on
>
> >> role and see a few features through in Ocata.  Given more and more
>
> >> glance-cores time sharing with other projects, I think we need some
>
> >> throttle in our review system. So, I'd like to help any new
> developers
>
> >> get their reviews up, that in turn will help the Glance community.
>
> >>
>
> >>
>
> >> Last but not the least, I have thoroughly enjoyed working in
> this role
>
> >> with all my fellow stackers, particularly glancers! So, a BIG
> thank you
>
> >> for having worked with me in making Glance better over the last
> couple
>
> >> of years.
>
> >>
>
> >>
>
> >
>
>
>
> --
>
>
>
> Thanks,
>
> Nikhil
>
>
>
>
>
> __
>
> OpenStack Development Mailing List (not for usage questions)
>
> Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> <http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> <http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev>
>
>
>
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 

Thanks,
Nikhil



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Searchlight] PTL Non-candidacy

2016-09-12 Thread Nikhil Komawar

Hi Travis,


Firstly, I would like to congratulate you for such an amazing piece of
work that you've lead to create.


Even though not very hands on over the last few months, I've kept myself
updated with the new developments in the projects and seen the team
grow. So, I am glad to say that you've done a brilliant job at creating
this credible team and a vibrant community.


Thank you for all the hard work & great input as the PTL, and for your
decision to stay core in the project! Hope to keep interacting with you
in a different capacity :)

On 9/13/16 1:00 AM, Tripp, Travis S wrote:
> Hi everybody,
>
> After an amazing ride that I believe has created a solid platform for a rich 
> and interactive search experience in OpenStack, I wanted to let everybody 
> know that I will not be nominating myself to be the Searchlight PTL for the 
> Ocata cycle. I will continue as a core reviewer and will support whoever is 
> the next PTL. 
>
> After 4 release cycles of solid and rapid development (Kilo, Liberty, Mitaka, 
> & Newton) we will be applying the 1.0 release tag in a few weeks. This marks 
> a significant achievement for this project, because we took a very 
> conservative approach to release numbering and waited to move past the 0.x 
> release tag until we felt like the project was ready for deployers to start 
> using it. We’ve achieved that milestone with the Newton release.
>
> With 1.0, Searchlight now provides:
>
> * Unified search and aggregation queries across:
>* Nova instances, flavors, hypervisors, & server groups
>* Glance images, snapshots, metadefs
>* Cinder volumes, snapshots
>* Neutron networks, ports, subnets, routers, security groups, & floating 
> IPs
>* Designate (DNS) Zones, recordsets
>* Swift container and object search (Experimental)
> * A horizon search panel (plugin)
> * A CLI via an OpenStack client plugin
> * Strong deployment management support via documentation and the CLI
>* Including zero downtime re-indexing and migration support
>
> This is all incredibly powerful and really changes the way you interact with 
> the cloud when you really start to use it, such as through the Searchlight UI 
> plugin for Horizon. Even so, I believe that we’ve barely started to scratch 
> the surface of what we can do with the search and aggregation [0] [1] 
> capabilities provided by Searchlight.
>
> I’m really excited to see where it goes from here!
>
> -Travis
>
>
> [0] 
> http://docs.openstack.org/developer/searchlight/searchlightapi.html#aggregations
> [1] For example, in a couple of hours I was able to use Searchlight to 
> include the number of instances that an image is use by in the Horizon images 
> table: http://imgur.com/a/l7S00
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 

Thanks,
Nikhil



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [glance] [elections] Glance PTL non-candidacy

2016-09-12 Thread Nikhil Komawar

Thank you Fei Long. It's always a pleasure working with you!


On 9/13/16 12:59 AM, Fei Long Wang wrote:
> Hi Nikhil,
>
> Thanks for your hard work as Glance PTL, you did a great job. And
> happy to know you will still work in OpenStack, see you around ;)
>
> On 12/09/16 18:08, Nikhil Komawar wrote:
>> Hi team,
>>
>>
>> Just wanted to share my decision for not running for PTL for Glance.
>> It's been great serving the community in this role however, there are
>> some personal and family matters that I need to attend to over the next
>> couple of months or so.
>>
>>
>> I think the Glance team has done great and we've quite a bunch of bright
>> developers who are helping push the project forward in the appropriate
>> direction. With Glare becoming separate project and Ocata being short
>> cycle, I anticipate the priorities being rather obvious to those who
>> have stayed in touch. I will be available to do the rightful handoff to
>> the incoming PTL (for Ocata) and update with Newton happenings once
>> we're done with a few important bugs that are being targeted for RC1.
>>
>>
>> I intend to stick around in Glance and related projects like
>> Searchlight, Glare, etc. However, I am planning to take a more hands on
>> role and see a few features through in Ocata.  Given more and more
>> glance-cores time sharing with other projects, I think we need some
>> throttle in our review system. So, I'd like to help any new developers
>> get their reviews up, that in turn will help the Glance community.
>>
>>
>> Last but not the least, I have thoroughly enjoyed working in this role
>> with all my fellow stackers, particularly glancers! So, a BIG thank you
>> for having worked with me in making Glance better over the last couple
>> of years.
>>
>>
>

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [glance] [elections] Glance PTL non-candidacy

2016-09-12 Thread Nikhil Komawar

Thanks Abhishek! I'm glad to have been of assistance and happy to help
further.


On 9/13/16 12:27 AM, Kekane, Abhishek wrote:
> Hi Nikhil,
>
> Thank you for your support, guidance and hard work as Glance PTL.
> I have enjoyed working with you and glad to know that you will be there to 
> help :)
>
> Thank you,
>
> Abhishek
>
> -----Original Message-
> From: Nikhil Komawar [mailto:nik.koma...@gmail.com] 
> Sent: Monday, September 12, 2016 11:39 AM
> To: OpenStack Development Mailing List
> Subject: [openstack-dev] [glance] [elections] Glance PTL non-candidacy
>
> Hi team,
>
>
> Just wanted to share my decision for not running for PTL for Glance.
> It's been great serving the community in this role however, there are some 
> personal and family matters that I need to attend to over the next couple of 
> months or so.
>
>
> I think the Glance team has done great and we've quite a bunch of bright 
> developers who are helping push the project forward in the appropriate 
> direction. With Glare becoming separate project and Ocata being short cycle, 
> I anticipate the priorities being rather obvious to those who have stayed in 
> touch. I will be available to do the rightful handoff to the incoming PTL 
> (for Ocata) and update with Newton happenings once we're done with a few 
> important bugs that are being targeted for RC1.
>
>
> I intend to stick around in Glance and related projects like Searchlight, 
> Glare, etc. However, I am planning to take a more hands on role and see a few 
> features through in Ocata.  Given more and more glance-cores time sharing 
> with other projects, I think we need some throttle in our review system. So, 
> I'd like to help any new developers get their reviews up, that in turn will 
> help the Glance community.
>
>
> Last but not the least, I have thoroughly enjoyed working in this role with 
> all my fellow stackers, particularly glancers! So, a BIG thank you for having 
> worked with me in making Glance better over the last couple of years.
>
>

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [glance] Periodically checking Glance image files

2016-09-12 Thread Nikhil Komawar

Hey Sergio,


Glad to know that you're not having any feature related issues (to me
this is a good sign). Based on your answers, it makes sense to require a
reliability solution for backend data (or some sort of health monitoring
for the user data).


So, I wonder what your thoughts are for such an audit system. At a first
glance, this looks rather not scalable, at least if you plan to do the
audit on all of the active images. Consider a deployment trying to run
this for around 100-500K active image records. This will need to be run
in batches, thus completing the list of records and saying that you've
done a full audit of the active image -- is a NP-complete problem (new
images can be introduced, some images can be updated in the meantime, etc.)

The failure rate is low, so a random (sparse check) on the image data
won't help either. Would a cron job setup to do the audit for smaller
deployments work? May be we can look into some known cron solutions to
do the trick?


On 9/12/16 4:18 PM, Sergio A. de Carvalho Jr. wrote:
> Hi Nikhil,
>
> Thanks so much for you response.
>
> 1) No, this is a private cloud.
> 2) Glance v1 (this problem has manifested itself in one of our oldest
> deployments, which is running Icehouse).
> 3) No, location is not exposed.
> 4) Glance is setup with the filesystem backend drive, using a Gluster
> volume mounted on the host..
> 5.1) Images were in active state, even though the image file had zero
> bytes.
> 5.2) very low, it may have happened only twice in the last year.
>
> Even if the location is not exposed, there are a number of things that
> can happen to the actual images files after they've been uploaded to
> Glance, without Glance noticing, depending how reliable your storage
> backend is. That's why I thought, in some circumstances, it would be
> useful to have some sort of background service checking that image
> files haven't been corrupted or gone missing altogether.
>
> Sergio
>
>
> On Mon, Sep 12, 2016 at 7:27 PM, Nikhil Komawar <nik.koma...@gmail.com
> <mailto:nik.koma...@gmail.com>> wrote:
>
>
> Hi Sergio,
>
> Thanks for reaching out. And this is an excellent question.
>
> Firstly, I'd like to mention that Glance is built-in (and if deployed
> correctly) is self-resilient in ensuring that you do NOT need an audit
> of such files. In fact, if any operator (particularly large scale
> operator) needs such a system we have a serious issue where
> potentially
> important /user/ data is likely to be lost resulting in legal
> issues (so
> please beware).
>
> Having said that, I'd like to start investigating more into your
> particular issue and see where we may be missing out in ensuring data
> integrity in Glance. Let me ask you a first few set of questions that
> will help us get an initial understanding:-
>
> 1) Are you a public cloud vendor; in particular, have you deployed
> glance to potentially non-trusted users? or is the case otherwise?
> 2) Are you deploying Glance v1 or Glance v2?
> 3) Have you exposed the "location" feature set (CRUD) to regular
> users?
> (if using API v2, have you enabled ``show_multiple_locations``
> configuration)
> 4) What backends have you configured Glance with and who has access to
> them? What is the resiliency or rotation (of disks) (for say capacity
> management) of your backend store system?
> 5) Sanity check on your issue:-
> 5.1) What are the image statues for which the image data files are
> missing?
> 5.2) What is the rate of error approximately (if you don't have
> specifics, info like rare, medium, often will help)
>
>
> We may have to dig a bit further into the issue but this set of info
> should help us narrow down the issue and determine if there are
> any gaps
> in Glance.
>
> P.S. Please use the tag "[glance]" in the subject line to help us
> get to
> your email faster.
>
> On 9/12/16 12:48 PM, Sergio A. de Carvalho Jr. wrote:
> > Hi all,
> >
> > Is there (or was there ever) any plans to implement in Glance a
> > service that would periodically check that the image files are still
> > available on the file system (or in whatever storage system being
> > used) and have the correct checksum?
> >
> > We had a few issues where an image file was removed from the
> > filesystem and that can go undetected for a long time until someone
> > tries to access that image, so we were wondering if it would be
> > possible (and if it would make sense) to implement some sort of
> > background service to periodic

Re: [openstack-dev] [glance] [elections] Glance PTL non-candidacy

2016-09-12 Thread Nikhil Komawar

Thanks Brian. I'm glad to be associated with OpenStack and Glance.


On 9/12/16 8:46 AM, Brian Rosmaita wrote:
> Nikhil,
>
> Thank you for all your hard work as Glance PTL (3 times!).  Glad to hear
> that you will be continuing to work in OpenStack, and especially that you
> plan to continue working with Glance.
>
> cheers,
> brian
>
> On 9/12/16, 2:08 AM, "Nikhil Komawar" <nik.koma...@gmail.com> wrote:
>
>> Hi team,
>>
>>
>> Just wanted to share my decision for not running for PTL for Glance.
>> It's been great serving the community in this role however, there are
>> some personal and family matters that I need to attend to over the next
>> couple of months or so.
>>
>>
>> I think the Glance team has done great and we've quite a bunch of bright
>> developers who are helping push the project forward in the appropriate
>> direction. With Glare becoming separate project and Ocata being short
>> cycle, I anticipate the priorities being rather obvious to those who
>> have stayed in touch. I will be available to do the rightful handoff to
>> the incoming PTL (for Ocata) and update with Newton happenings once
>> we're done with a few important bugs that are being targeted for RC1.
>>
>>
>> I intend to stick around in Glance and related projects like
>> Searchlight, Glare, etc. However, I am planning to take a more hands on
>> role and see a few features through in Ocata.  Given more and more
>> glance-cores time sharing with other projects, I think we need some
>> throttle in our review system. So, I'd like to help any new developers
>> get their reviews up, that in turn will help the Glance community.
>>
>>
>> Last but not the least, I have thoroughly enjoyed working in this role
>> with all my fellow stackers, particularly glancers! So, a BIG thank you
>> for having worked with me in making Glance better over the last couple
>> of years.
>>
>>
>> -- 
>>
>> Cheers,
>> Nikhil
>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [glance] Bug days next week

2016-09-12 Thread Nikhil Komawar

Just a gentle reminder, the bug days start Tuesday September 13th.

https://etherpad.openstack.org/p/newton-glance-sept-bug-days


P.S. In some parts of the world, this day has already started.


On 9/7/16 3:54 PM, Nikhil Komawar wrote:
> Hi all,
>
>
> I would like to propose bug days for Glance next week Tuesday 13th
> September and Wednesday 14th September (during your work hours / in your
> time zone).
>
>
> We've a plenty of bugs to address [1, 2, 3] and looks like the the right
> time in the cycle when we would get a good benefit of these bug days. I
> would encourage people to focus on Glance server bugs rather than client
> and store bugs during these days. Nevertheless, you are free to choose
> what best suits your needs.
>
>
> RC1 is supposed to be targeted on Thursday Sept 15th and it would be a
> good time to triage some critical bugs for the same.
>
>
> Additionally, this is an excellent opportunity to all those who are
> looking to get involved, become a glance-core or just make some more
> contributions to Glance.
>
>
> If you happen to fix an important bug and think that we need to include
> it as a part of a Glance RC release, please drop me a note on IRC and
> wait for my update. Either I will propose a topic change to
> "newton-rc-potential" indicating that it has been considered strongly to
> be a part of the release or I may leave a comment indicating why we
> haven't considered so. Please do NOT make the topic to
> "newton-rc-potential" yourself as it will be used while coordinating the
> release work and unexpected reviews under that topic will delay or
> disrupt the release process.
>
>
> If you do not have time to propose a review and have found a bug that
> could be a good candidate for Newton RC, then please "tag" that bug in
> launchpad to have the tag named "newton-rc-potential" (this tag has been
> added to official tags list). The bug team or the Glance core team will
> then consider proposing fixes for these bugs.
>
>
> We will use etherpad to collaboratively add notes and updates for this
> event here [4]. Please see my official entry for this event at [5].
>
>
> As always, feel free to reach out for questions and comments.
>
>
> [1] https://bugs.launchpad.net/glance/
>
> [2] https://bugs.launchpad.net/glance-store
>
> [3] https://bugs.launchpad.net/python-glanceclient/
>
> [4] https://etherpad.openstack.org/p/newton-glance-sept-bug-days
>
> [5] https://review.openstack.org/366923
>
>

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [glance] Periodically checking Glance image files

2016-09-12 Thread Nikhil Komawar

Hi Sergio,

Thanks for reaching out. And this is an excellent question.

Firstly, I'd like to mention that Glance is built-in (and if deployed
correctly) is self-resilient in ensuring that you do NOT need an audit
of such files. In fact, if any operator (particularly large scale
operator) needs such a system we have a serious issue where potentially
important /user/ data is likely to be lost resulting in legal issues (so
please beware).

Having said that, I'd like to start investigating more into your
particular issue and see where we may be missing out in ensuring data
integrity in Glance. Let me ask you a first few set of questions that
will help us get an initial understanding:-

1) Are you a public cloud vendor; in particular, have you deployed
glance to potentially non-trusted users? or is the case otherwise?
2) Are you deploying Glance v1 or Glance v2?
3) Have you exposed the "location" feature set (CRUD) to regular users?
(if using API v2, have you enabled ``show_multiple_locations``
configuration)
4) What backends have you configured Glance with and who has access to
them? What is the resiliency or rotation (of disks) (for say capacity
management) of your backend store system?
5) Sanity check on your issue:-
5.1) What are the image statues for which the image data files are missing?
5.2) What is the rate of error approximately (if you don't have
specifics, info like rare, medium, often will help)

We may have to dig a bit further into the issue but this set of info
should help us narrow down the issue and determine if there are any gaps
in Glance.

P.S. Please use the tag "[glance]" in the subject line to help us get to
your email faster.

On 9/12/16 12:48 PM, Sergio A. de Carvalho Jr. wrote:
> Hi all,
>
> Is there (or was there ever) any plans to implement in Glance a
> service that would periodically check that the image files are still
> available on the file system (or in whatever storage system being
> used) and have the correct checksum?
>
> We had a few issues where an image file was removed from the
> filesystem and that can go undetected for a long time until someone
> tries to access that image, so we were wondering if it would be
> possible (and if it would make sense) to implement some sort of
> background service to periodically check if all images found in the
> database can be retrieved successfully.
>
> Thoughts?
>
> Sergio
>
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>

-- 

Thanks,
Nikhil

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [glance] [elections] Glance PTL non-candidacy

2016-09-12 Thread Nikhil Komawar

Hi team,


Just wanted to share my decision for not running for PTL for Glance.
It's been great serving the community in this role however, there are
some personal and family matters that I need to attend to over the next
couple of months or so.


I think the Glance team has done great and we've quite a bunch of bright
developers who are helping push the project forward in the appropriate
direction. With Glare becoming separate project and Ocata being short
cycle, I anticipate the priorities being rather obvious to those who
have stayed in touch. I will be available to do the rightful handoff to
the incoming PTL (for Ocata) and update with Newton happenings once
we're done with a few important bugs that are being targeted for RC1.


I intend to stick around in Glance and related projects like
Searchlight, Glare, etc. However, I am planning to take a more hands on
role and see a few features through in Ocata.  Given more and more
glance-cores time sharing with other projects, I think we need some
throttle in our review system. So, I'd like to help any new developers
get their reviews up, that in turn will help the Glance community.


Last but not the least, I have thoroughly enjoyed working in this role
with all my fellow stackers, particularly glancers! So, a BIG thank you
for having worked with me in making Glance better over the last couple
of years.


-- 

Cheers,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [architecture] First meeting happened -- Regularly scheduled Thursdays at 1900

2016-09-11 Thread Nikhil Komawar


Thanks for this email Clint!

I added a courtesy reminder section where people who wish to join and be
notified prior to start of the meeting can do so. I encourage everyone
to consider adding their nicks and the meeting chair to ping them. This
will help everyone avoid maintain another meeting on the calendar and
get notified on irc just when the meeting is about to start.

On 9/11/16 6:27 PM, Clint Byrum wrote:
> FYI, we had our first Architecture WG meeting this past Thursday. I want
> to thank everyone who was able to make it. I hope that we'll see
> increased attendance and be able to begin selecting specifications to
> discuss and work on starting with our next meeting.
>
> The agenda is available here:
>
> https://wiki.openstack.org/wiki/Meetings/Arch-WG
>
> Important topics we're expecting this week:
>
> * Whether or not to have an alternative meeting time for better time
>   zone coverage.
> * Whether or not to abandon the cross-project spec and instead just
>   adopt what is available now as an internal charter.
> * What to start focusing on designing/documenting/working
>
> I hope to see more of you there on #openstack-meeting-alt this Thursday.
> Thanks!
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Timeframe for future elections & "Release stewards"

2016-09-09 Thread Nikhil Komawar



On 9/9/16 4:42 AM, Thierry Carrez wrote:
> John Griffith wrote:
>> I think Sean Dague made some really good points and I'd tend to lean
>> that way.  Honestly charters, bylaws, governance etc shift or are
>> rewritten fairly often.  Why not just change when we do elections to
>> correspond with releases and keep the continuity that we have now.  Is
>> there a problem with the existing terms and cycles that maybe I'm missing?
> AFAICT this is not what Sean is proposing. He is saying that we should
> run elections in the weeks before Summit as usual, but the newly-elected
> PTL would /not/ take over the current PTL until 3 months later when the
> next development branches are opened.
>
> While it's true that there are projects with a lot of continuity and
> succession planning, with the old PTL staying around after they have
> been replaced, there are also a fair share of projects where the PTL is
> replaced by election and either rage-quits or lowers their involvement
> significantly as a result. I'd rather have the /possibility/ to separate
> the PTL from the release steward role and ensure continuity.
>
> That doesn't prevent you from doing it Nova-style and use the PTL as the
> release steward. It just lets you use someone else if you want to. A bit
> like keeping a headphone jack. Options.

LOL. May be we need to name the release steward as "headphone jack" then!

>

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [stable] [all] Regarding string freeze and back ports involving translatable strings

2016-09-09 Thread Nikhil Komawar

I have had some questions offline so, I think documenting the theory,
interpretations and POC will be helpful in our release schedule pages to
get this practice consistent across projects. If not required (or if the
process is subjective) we do not necessarily have to enforce strict
process, but we do have to make sure everyone reading the schedule are
on the same page and not wondering twice or looking for ML emails.

http://releases.openstack.org/newton/schedule.html

https://releases.openstack.org/ocata/schedule.html



On 9/9/16 3:12 PM, Matt Riedemann wrote:
> On 9/9/2016 1:58 PM, Ben Swartzlander wrote:
>
>> On 09/08/2016 08:37 PM, Matt Riedemann wrote:
>>
>>> On 9/8/2016 7:05 PM, Ravi, Goutham wrote:
>>>
 Hi,







 I was looking for some clarity around backports of bug fixes that

 qualify the stable branch policy [1].

 





 What is the policy if the fix introduces a new translatable string or

 modifies an existing one?



 The guidelines in Release management [2]

 

 regarding string freeze do not specifically call this scenario out. I

 see that while translatable strings are mostly avoided, some projects

 have been merging changes to stable branches with introduction of new

 translatable strings.







 The question is reminiscent of one posed in the ML a few releases ago

 [3];

 





 but applies to stable branches. Should we allow changes to translatable

 strings for bug fixes that matter, or is it better to always deny them

 for the sake of translation accuracy?

>>>
>>>
>>> The former IMO, a high severity bug fix trumps a translation. Note that
>>>
>>> some projects are translated on the stable branches too, I know this is
>>>
>>> the case for Nova.
>>>
>>>
>>>
>>> If it's a user-facing change, like an error message in the API, then it
>>>
>>> might require a bit more careful consideration, but if it's just a log
>>>
>>> message marked for translation that an end user of the API wouldn't see
>>>
>>> anyway, then I think it's fine to backport it.
>>>
>>
>>
>> So this stance makes sense to me, but I can't reconcile it with the
>>
>> "hard string freeze" rules. Is the theory that after we release, the
>>
>> string freeze ends for the stable branch, and that the hard string
>>
>> freeze only exists for that 3 week period between RC1 and final release,
>>
>> or is the theory that hard string freeze is always subject to exceptions
>>
>> for "critical" bug fixes?
>>
>>
>>
>> -Ben Swartzlander
>>
>>
>>






 [1]

 http://docs.openstack.org/project-team-guide/stable-branches.html#appropriate-fixes









 [2]
 http://docs.openstack.org/project-team-guide/release-management.html



 [3]

 http://lists.openstack.org/pipermail/openstack-dev/2015-September/073942.html













 Thanks,



 Goutham







 __





 OpenStack Development Mailing List (not for usage questions)

 Unsubscribe:

 openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



>>>
>>>
>>>
>>>
>>
>>
>>
>>
>> __
>>
>> OpenStack Development Mailing List (not for usage questions)
>>
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>>
>
>
> I treat it as the former.
>
>
>
>
>


-- 

Thanks,
Nikhil



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Timeframe for future elections & "Release stewards"

2016-09-09 Thread Nikhil Komawar



On 9/9/16 11:32 AM, Thierry Carrez wrote:
> Thierry Carrez wrote:
>> [...]
>> One interesting side-effect is that since the timing of the election
>> period (for PTL and TC positions) is defined in the TC charter[3]
>> relative to the *Summit*, it means that (unless we change this) we'll
>> now run elections to renew PTL and TC positions in the middle of the
>> cycle. Crazy, right ? That's what I first thought. But after discussing
>> it with various people, this is not as crazy as it sounds.
>> [...]
> Oh. Wait. *Some* of the wording in the charter actually mentions "design
> summit" -- since that's dissolved into two events, we kind of need to to
> alter the wording there anyway. There is no status quo.
>
> So we'll have to discuss whether it's better to define our next PTL/TC
> elections relative to the PTG (happening Feb 20-24, 2017) or to the
> Summit (happening May 8-12, 2017), or to something completely different
> (like the release date).
>
> I still think it's simpler to run relative to Summit (so that the PTLs
> running for election in the coming days will have a normal 6-month
> term), but the other solution would work too.
>
> Personally I care about having a point person to handle a release cycle
> from the preparation stages (months before the PTG) to the post-release
> stage (months after release). I don't care as much about exactly when
> the name of the person holding the PTL title (may) change... since there


"""
> is no perfect timing for that, you're always in the middle of something.
>
"""

"no perfect timing..." this can go in as thought of the day and I will
acknowledge +1000 to it.

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Timeframe for future elections & "Release stewards"

2016-09-08 Thread Nikhil Komawar




On 9/8/16 7:42 AM, Sean Dague wrote:
> On 09/08/2016 05:00 AM, Thierry Carrez wrote:
>> Sean Dague wrote:
> 
>> So... the difference between your proposal and mine is: you force the
>> PTL to be the release steward (rather than having a choice there), and
>> introduce a delay between election and start of authority for the PTL.
>>
>> I don't see that delay as a good thing. You would elect in April a PTL
>> whose authority over the project would start in August. That sounds a
>> bit weird to me. I'd rather say that the authority of the PTL starts
>> when he is elected, and not introduce a delay.
>>
>> I don't see *forcing* the PTL to be the release steward to be a good
>> thing either. The just-elected PTL can totally be the release steward
>> for the upcoming cycle -- actually, that is how my proposal would work
>> by default: the PTL elected around Boston would be the default release
>> steward for Q, and the PTL elected around Sydney would be the default
>> release steward for R. But I'd rather allow for some flexibility here,
>> in case the PTL prefers to delegate more of his work. I also think
>> allowing for more leadership roles (rather than piling it all on the
>> PTL) helps growing a stronger leadership pipeline.
>>
>> In summary, I see drawbacks to your variant, and I fail to see any
>> benefits... Am I missing something ?
> I can only bring my own experience from projects, which is to expose
> projects to succession planning a bit earlier, but otherwise keep things
> the same. Both with working in the QA team, and in Nova, usually the
> standing PTL starts telling folks about half way through their final
> term that they aren't going to run again. And there ends up being a
> bunch of private team conversations to figure out who else is
> interested. Often those folks need to clear some things off their plate.
> So there is some completely private indication of who might be the next
> PTL. However, nothing is made official, and no one wants to presume
> until an actual election happens months later.
>
> When succession planning doesn't go well, you get to nomination week,
> and you find out the current PTL isn't running, and there are two days
> of mad scramble trying to figure out who is going to run.
>
> Forcing the PTL-next conversation back some amount of time means it
> matches the way I've seen succession planning work in projects for the
> best handoff.
>
> I feel like projects and PTLs do already delegate the things they can
> and want to. It's not clear to me that creating another title of release
> steward is going to dramatically change that. Maybe it's an active
> suggestion to delegate that role out? Or that another title helps
> convince employers that someone needs to end up at the PTG?

I think yes, an active suggestion to delegate that role out. My
experiences tell me that release work and PTL work may not always play
fair with each others. It is very useful to have someone else take care
of the releases stuff while a PTL will try to co-ordinate other pieces
of the projects.

Honestly, I think the "release stewards" concept looks more of a formal
approach to recognize liaisons. I know projects internally appreciate
what the individual liaisons do but I haven't observed one too many
instances where such individuals get wider visibility for their work.
Having another individual take care of this complicated release work
while the PTL focuses on planning and feature work -- looks like a good
idea to handle two ends of spectrum; one which is about planning,
discussions, setting trade-offs for all the different kinds of impacts a
new introduction may have, cross collaboration etc. and the other is
about getting things done, a more focused and prioritize
what-matters-only-now work.


> I'm also not very concerned about delayed authority of the PTL. Peaceful
> handoff should be a pretty basic tenant in projects. Knowing about it
> for a longer time shouldn't be a big deal. If it causes giant strife to
> pass the torch from one PTL to the next there is something else going
> wrong in that project. In the few cases I'm familiar with in which a
> standing PTL lost an election, the relationship between that PTL and the
> PTL-next was fine.
>
> Again, these are personal experiences from the projects I'm actively
> involved with, or collaborate with the most.
>
>   -Sean
>
>
>


-- 

Thanks,
Nikhil



__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Timeframe for future elections & "Release stewards"

2016-09-08 Thread Nikhil Komawar

Good comment and I have an answer inline.

On 9/8/16 2:41 PM, Hongbin Lu wrote:
>
>> -Original Message-
>> From: Thierry Carrez [mailto:thie...@openstack.org]
>> Sent: September-08-16 5:00 AM
>> To: openstack-dev@lists.openstack.org
>> Subject: Re: [openstack-dev] [all] Timeframe for future elections &
>> "Release stewards"
>>
>> Sean Dague wrote:
>>> On 09/07/2016 12:27 PM, Thierry Carrez wrote:
 Barrett, Carol L wrote:
> From: Sean Dague [mailto:s...@dague.net]
>> I think another option would be to run the PTL election early, but
>> just don't have the turn over happen until the master release
>> opens
>> up. The current transition period is > > > actually quite short as
>> noted by the comments around how design summit planning happens. Having
>> the PTL-next elected half way through the cycle, but having PTL
>> current > still > own landing the current release actually provides a
>> lot more transition time.
>>  -Sean
> I had a similar thought to Sean's, with a few changes. Why not have
>> a PTL own the release from start to finish, with the PTL for the next
>> release getting elected as above. In this model, it would probably be
>> advisable (or a guideline) that a PTL not run for 2 cycles in a row,
>> because the work load would be unmanageable. This approach could help
>> to grow a stronger leadership pipeline for each project and provide
>> more opportunities for people in the team to grow their skills and take
>> on leadership.
 The drawback of this approach is that it breaks the governance model
 around project teams. You need a "the buck stops here" person (even
 if that power is seldom used). But you can't have two -- what
>> happens
 if they disagree ?

 So it's simpler to have a single PTL at all times and one or two
 release liaisons at all times. Could be the same person though.
>>> It doesn't give you 2 PTLs. It gives you PTL-next that gets to make
>>> decisions on master once it opens up, and guides it until it's a
>>> stable branch. It doesn't seem like it breaks anything to me.
>> So... the difference between your proposal and mine is: you force the
>> PTL to be the release steward (rather than having a choice there), and
>> introduce a delay between election and start of authority for the PTL.
>>
>> I don't see that delay as a good thing. You would elect in April a PTL
>> whose authority over the project would start in August. That sounds a
>> bit weird to me. I'd rather say that the authority of the PTL starts
>> when he is elected, and not introduce a delay.
> If the authority of the PTL starts in the middle of a cycle, what happen if 
> the just-elected PTL disagree with what were planned by the previous PTL? 
> Does the just-elected PTL have authority to override what were planned? For 
> contributors, it is confusing to have two PTLs in one cycle. They might 
> follow the instruction from one PTL to setup the plan for the whole cycle. 
> Then, in the second half of the cycle, the new PTL give a totally different 
> instruction for the same item. As a result, the plan needs to be changed or 
> extra efforts are needed to ensure the new PTL agrees with the original plan. 
> In this case, introducing "release stewards" doesn't solve the problem 
> because this new role doesn't have final says.

Firstly, I'd like to say that the wording is bit strong here but I can
see where it may be coming from.

To be fair to all (i.e. generalizing this a bit), I think the PTL is
more of a guide than authority. Nevertheless, veto "does" belong to the
PTL but too many veto-s means misuse of authority and the veto loses its
value. So, a PTL, in most cases, doesn't give 'instructions' (well
unless you are doing fixed-timeline work like releases), PTL is supposed
to facilitate with planning, co-coordinating different interest parties,
determining the priorities/preferences, make educated guesses for the
feature and core bandwidth, etc.

So.. in a good coherent community (which is what each project should aim
for) we won't have drastically varying decisions during the transition
phase (PTL elections). Also, the elections should indicate that the new
PTL should respect the decisions that were taken by the former one.
Dissolving the power (or rights) from the PTL to more people in the team
(like in this case the release stewards) will ensure a check on anyone
having radical (very different) ideas in the middle of a running cycle.

To be even more specific, with this new approach, the new PTL gets
enough time to focus on new specs, proposals in backlog, bugs that will
increase there relevance in the upcoming months etc. and put up a strong
agenda or timeline for the next release. This works great for
particularly mature projects but I'm sure newer projects don't have much
to lose either. Newer projects will usually have smaller teams, may even
have the same set of people/stewards/PTL for a few cycles and when these
projects mature they

[openstack-dev] [glance] Newton RC reviews and releases

2016-09-07 Thread Nikhil Komawar

Hi team,


The RC period for a release spans multiple weeks, see Newton schedule
here [1]. There are about 4 more weeks in Newton when potential RC
releases could take place. The RC1 is bound to happen next week and
there will most likely be a RC2 with translations. If there are more
critical fixes to be done during this phase we would need to accommodate
in either of the two or in rare case propose another candidate.


Hence, to smoothen the release process I've started changing the topic
to "newton-rc-potential" of certain reviews that I thought are
important; they can thus be discovered using the link [2]. Core
reviewers, please give a preferential review to these. Also, if you are
a Glance core, please feel free to change the topics of reviews that you
think are RC critical respectively. If you are not a Glance core and
think that a review could be part of the Newton release, please ping me
or one of the Glance cores you know, to consider it to be part of
newton-rc-potential group.


Please reach out for any outstanding questions or comments.


[1] https://releases.openstack.org/newton/schedule.html

[2]
https://review.openstack.org/#/q/status:open+project:openstack/glance+topic:newton-rc-potential


-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [glance] Bug days next week

2016-09-07 Thread Nikhil Komawar

Hi all,


I would like to propose bug days for Glance next week Tuesday 13th
September and Wednesday 14th September (during your work hours / in your
time zone).


We've a plenty of bugs to address [1, 2, 3] and looks like the the right
time in the cycle when we would get a good benefit of these bug days. I
would encourage people to focus on Glance server bugs rather than client
and store bugs during these days. Nevertheless, you are free to choose
what best suits your needs.


RC1 is supposed to be targeted on Thursday Sept 15th and it would be a
good time to triage some critical bugs for the same.


Additionally, this is an excellent opportunity to all those who are
looking to get involved, become a glance-core or just make some more
contributions to Glance.


If you happen to fix an important bug and think that we need to include
it as a part of a Glance RC release, please drop me a note on IRC and
wait for my update. Either I will propose a topic change to
"newton-rc-potential" indicating that it has been considered strongly to
be a part of the release or I may leave a comment indicating why we
haven't considered so. Please do NOT make the topic to
"newton-rc-potential" yourself as it will be used while coordinating the
release work and unexpected reviews under that topic will delay or
disrupt the release process.


If you do not have time to propose a review and have found a bug that
could be a good candidate for Newton RC, then please "tag" that bug in
launchpad to have the tag named "newton-rc-potential" (this tag has been
added to official tags list). The bug team or the Glance core team will
then consider proposing fixes for these bugs.


We will use etherpad to collaboratively add notes and updates for this
event here [4]. Please see my official entry for this event at [5].


As always, feel free to reach out for questions and comments.


[1] https://bugs.launchpad.net/glance/

[2] https://bugs.launchpad.net/glance-store

[3] https://bugs.launchpad.net/python-glanceclient/

[4] https://etherpad.openstack.org/p/newton-glance-sept-bug-days

[5] https://review.openstack.org/366923


-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [release] proposing adding Tony Breeds to "Release Managers" team

2016-09-06 Thread Nikhil Komawar

+1. def.


I have always found his reviews quite detailed and constructive.


On 9/6/16 11:36 AM, Doug Hellmann wrote:
> Team,
>
> I would like to add Tony Breeds to the "Release Managers" team in
> gerrit. This would give him +2 permissions on openstack-infra/release-tools
> and on openstack/releases. I feel his reviews on both of those repos
> have already demonstrated a good attention to detail, especially
> of the release schedule and processes.
>
> Please respond below with +1 or -1.
>
> Thanks,
> Doug
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [glance] [nova] Query on image signing support

2016-09-05 Thread Nikhil Komawar

Good questions.

Please ask them here [1]. I think we will get answers and be able to
document them at the same time.

[1] https://review.openstack.org/#/c/314718/

On 9/5/16 9:09 AM, White, Darren wrote:
> Hi,
>
> Does anyone know if signed images in Glance will be supported in these use 
> cases:
>
> 1. Verifying a signed image downloaded via Glance CLI (glance image-download 
> ).
>
> 2. Creating a snapshot in Nova, and Nova signs the image. Nova will upload 
> the signed image to Glance, along with the signature properties. Glance will 
> then verify the signed image.
>
> 3. Nova verifying a signed image which is requested from Glance (i.e nova 
> boot).
>
>
>
> Thanks, Darren.
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [glance] Newton-3 released and RC-1 phase start

2016-09-02 Thread Nikhil Komawar

There are a few more details around critical fixes, libraries and their
releases based on critical fixes, stable branches, dates, etc. here
http://lists.openstack.org/pipermail/openstack-dev/2016-September/102829.html


On 9/2/16 12:03 PM, Nikhil Komawar wrote:
> Hi all,
>
>
> This is a email notice being sent to let all know that Newton 3 for
> Glance has been released yesterday [1]. The RC-1 phase has begun and at
> this time we are respecting all the freezes that are introduced as per
> the release schedule [2].
>
>
> Refresher (to those who are already familiar):
>
>   * At this point in the cycle we're in Feature freeze, no more client
> or store release until R-0 as well as string and requirements freeze.
>
>   * Hence, please refrain from merging any of the above changes. No
> freeze exceptions have been granted for Glance. Also, please do not
> merge trivial commits during this phase. We should be focusing time and
> energy on important bugs and any likely regressions that may arise in rc-1.
>
>   * The stable/newton branch will be cut at rc-1 until then, feel free
> to -2 changes that are not going to get in. But please *remember* to
> lift your -2s ASAP when the freeze is taken off.
>
>   * Although not needed as I've covered the needed points above, only if
> you've interest you can read up on more details at [3]
>
>
> As always, welcome to reach out for questions and comments.
>
>
> [1] https://review.openstack.org/#/c/363930/
>
> [2] https://releases.openstack.org/newton/schedule.html
>
> [3]
> http://docs.openstack.org/project-team-guide/release-management.html#typical-development-cycle-schedule
>
>

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [glance] Newton-3 released and RC-1 phase start

2016-09-02 Thread Nikhil Komawar

Hi all,

This is a email notice being sent to let all know that Newton 3 for
Glance has been released yesterday [1]. The RC-1 phase has begun and at
this time we are respecting all the freezes that are introduced as per
the release schedule [2].

Refresher (to those who are already familiar):

* At this point in the cycle we're in Feature freeze, no more client
or store release until R-0 as well as string and requirements freeze.

* Hence, please refrain from merging any of the above changes. No
freeze exceptions have been granted for Glance. Also, please do not
merge trivial commits during this phase. We should be focusing time and
energy on important bugs and any likely regressions that may arise in rc-1.

* The stable/newton branch will be cut at rc-1 until then, feel free
to -2 changes that are not going to get in. But please *remember* to
lift your -2s ASAP when the freeze is taken off.

* Although not needed as I've covered the needed points above, only if
you've interest you can read up on more details at [3]

As always, welcome to reach out for questions and comments.

[1] https://review.openstack.org/#/c/363930/

[2] https://releases.openstack.org/newton/schedule.html

[3]
http://docs.openstack.org/project-team-guide/release-management.html#typical-development-cycle-schedule

Thanks,
Nikhil

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [glance] Reviews in queue for newton-3

2016-08-31 Thread Nikhil Komawar

Hi all,


I've proposed a release patch up [1] where I am collecting all the
reviews that are in queue and you'd like them in Newton 3. Please leave
a comment up there and I will try to get to reviewing it soon. Based on
the progress, time available, freeze, etc. a determination about the
feasibility of it making into Newton will be done and if the review link
is posted on it in the next 4 hours, you'd expect a note on it
indicating if it will make it or otherwise.

Thanks for your co-operation and appreciate all the help in setting up
Newton release!


[1] https://review.openstack.org/#/c/363930/


-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [glance] store and client stable branches for newton

2016-08-30 Thread Nikhil Komawar

Hi,

The stable/newton has been cut and respective commits have merged for
both store and client [1]. Please feel free to merge any commits on
master that were pending however, note that we won't be releasing any
libraries out until R-0 when the freeze on libraries stops.

Let me know if there are questions.

[1] https://review.openstack.org/#/q/topic:create-newton


-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [glance] Barcelona summit space requirements and session planning etherpad

2016-08-30 Thread Nikhil Komawar

This was sent earlier in the day. Please note the final request for
schedule sent: FB: 2, WR: 2, CM: 1


Also, a request was made to have all Glance sessions on same day for the
convenience of the audience willing to show up (be in the same
place/floor/etc.) and request for the contributors' meetup to be on
Friday morning rather than afternoon so that participants can choose to
attend other contributors' meetup in the afternoon or leave early. This
was based on the experience from Austin summit where many participants
had to leave in the middle of Glance's CM to attend some other and then
came back. Hopefully, this plan works for the majority this time.


On 8/29/16 6:43 PM, Nikhil Komawar wrote:
> Just a friendly reminder that I will be sending the final summit
> planning request for slots for Glance first thing tomorrow. So, please
> cast your vote if haven't already. Thanks!
>
>
> From the looks of it, the current winner looks to be FB: 2, WR: 2, CM: 1
> (Friday afternoon) -- but this could change.
>
> https://etherpad.openstack.org/p/ocata-glance-summit-planning
>
>
> On 8/25/16 11:58 AM, Nikhil Komawar wrote:
>> Hi,
>>
>>
>> Just wanted to point out to those who haven't been to Glance meetings in
>> the past couple of weeks that we've to submit space requirements for the
>> Barcelona design summit early next week. I've listed the constraints
>> poised in front of us in the planning etherpad [1]. Please see the top
>> portion of this etherpad under "Layout Proposal" to either propose or
>> vote on the layout proposal options to help us collaboratively determine
>> the space needs for Glance. Currently there are 2 proposals and if you
>> don't have any other in mind, please cast your vote on the given.
>>
>>
>> I need the votes by EOD on Monday 29th Aug and will be sending our final
>> space requirement request first thing on Tuesday 30th.
>>
>>
>> On another note, if you want to start proposing sessions for the summit
>> feel free to scroll to the bottom of the etherpad for the template and
>> the slots for the topics.
>>
>>
>> Let me know if you've any questions.
>>
>>
>> [1] https://etherpad.openstack.org/p/ocata-glance-summit-planning
>>
>>

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [glance] Barcelona summit space requirements and session planning etherpad

2016-08-29 Thread Nikhil Komawar

Just a friendly reminder that I will be sending the final summit
planning request for slots for Glance first thing tomorrow. So, please
cast your vote if haven't already. Thanks!


>From the looks of it, the current winner looks to be FB: 2, WR: 2, CM: 1
(Friday afternoon) -- but this could change.

https://etherpad.openstack.org/p/ocata-glance-summit-planning


On 8/25/16 11:58 AM, Nikhil Komawar wrote:
> Hi,
>
>
> Just wanted to point out to those who haven't been to Glance meetings in
> the past couple of weeks that we've to submit space requirements for the
> Barcelona design summit early next week. I've listed the constraints
> poised in front of us in the planning etherpad [1]. Please see the top
> portion of this etherpad under "Layout Proposal" to either propose or
> vote on the layout proposal options to help us collaboratively determine
> the space needs for Glance. Currently there are 2 proposals and if you
> don't have any other in mind, please cast your vote on the given.
>
>
> I need the votes by EOD on Monday 29th Aug and will be sending our final
> space requirement request first thing on Tuesday 30th.
>
>
> On another note, if you want to start proposing sessions for the summit
> feel free to scroll to the bottom of the etherpad for the template and
> the slots for the topics.
>
>
> Let me know if you've any questions.
>
>
> [1] https://etherpad.openstack.org/p/ocata-glance-summit-planning
>
>

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [glance] Priority reviews for the upcoming n-3 release next week

2016-08-25 Thread Nikhil Komawar

Hi,


In today's weekly meeting, I've listed some of the priority reviews that
the reviewers, especially glance-cores, should focus on the coming few
days for the Newton-3 release next week [1]. We will be evaluating the
reviews that are likely to merge or otherwise in the next few days and
should have the final list by EOD Monday 29th. Given all the constraints
in mind, I am planning to propose the n-3 hash to the release team on
EOD Wednesday Aug 31st unless any critical issues come up [2]. So,
please make sure you keep your patches up to date and ready for review
if you need them in Newton.


Also, please stop proposing trivial fixes at this stage in the cycle as
such things put load on the gate and are detrimental to development work
in the community, not just Glance. Besides, having trivial fixes in
review queue distracts reviewers and presents an awkward view of the
review dashboard, again this is something that hampers productivity.


If you have WIP patches and are not planning to target it to Glance for
Newton or otherwise, please make sure you take some time to abandon
those patches. Cleaning up the queue yourself, will help the glance team
a long way -- kindly don't just rely on the PTL, release liaison or the
cores to do the cleaning for you.


[1]
http://eavesdrop.openstack.org/meetings/glance/2016/glance.2016-08-25-14.00.html
[2] http://releases.openstack.org/newton/schedule.html

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [glance] Barcelona summit space requirements and session planning etherpad

2016-08-25 Thread Nikhil Komawar

Hi,


Just wanted to point out to those who haven't been to Glance meetings in
the past couple of weeks that we've to submit space requirements for the
Barcelona design summit early next week. I've listed the constraints
poised in front of us in the planning etherpad [1]. Please see the top
portion of this etherpad under "Layout Proposal" to either propose or
vote on the layout proposal options to help us collaboratively determine
the space needs for Glance. Currently there are 2 proposals and if you
don't have any other in mind, please cast your vote on the given.


I need the votes by EOD on Monday 29th Aug and will be sending our final
space requirement request first thing on Tuesday 30th.


On another note, if you want to start proposing sessions for the summit
feel free to scroll to the bottom of the etherpad for the template and
the slots for the topics.


Let me know if you've any questions.


[1] https://etherpad.openstack.org/p/ocata-glance-summit-planning


-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [glance] [osc] an important regression related to python-glanceclient 2.4.0

2016-08-19 Thread Nikhil Komawar

Hi,


Recently a bug [1] was discovered affecting openstack client that
resulted into python-glanceclient not being compatible with the later.


As this issue contains complexity more than what meets the eye a revert
[2] to a commit that recently introduced this bug has been proposed.
Nevertheless, we would like to know why that revert is helping as it's
subsiding an underlying issue.


While we dig more into the details, a solution to help the packagers,
operators, different projects, etc. has been proposed via commits [3,
4]. Please consider the global requirements sync as a short term
solution for this issue/bug until we provide a cleaner solution.


You are welcome to drop by on #openstack-glance or reach out via email,
if having issues and bug isn't sufficient source of information.


[1] https://bugs.launchpad.net/python-glanceclient/+bug/1614971
[2] https://review.openstack.org/357624
[3] https://review.openstack.org/357937
[4] https://review.openstack.org/357955

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] versioning the api-ref?

2016-08-18 Thread Nikhil Komawar

I guess the intent was to indicate the need for indicating the micro or
in case of Glance minor version bump when required.

The API isn't drastically different, there are new and old elements as
shown in the Nova api ref linked.

On 8/12/16 5:49 AM, Sean Dague wrote:
> On 08/11/2016 06:02 PM, Brian Rosmaita wrote:
>> I have a question about the api-ref. Right now, for example, the new
>> images v1/v2 api-refs are accurate for Mitaka.  But DocImpact bugs are
>> being generated as we speak for changes in master that won't be
>> available to consumers until Newton is released (unless they build from
>> source). If those bug fixes get merged, then the api-ref will no longer
>> be accurate for Mitaka API consumers (since it's published upon update).
> I'm confused about this statement.
>
> Are you saying that the Glance v2 API in Mitaka and Newton are different
> in some user visible ways? But both are called the v2 API? How does an
> end user know which to use?
>
> The assumption with the api-ref work is that the API document should be
> timeless (branchless), and hence why building from master is always
> appropriate. That information works for all time.
>
> We do support microversion markup in the document, you can see some of
> that in action here in the Nova API Ref -
> http://developer.openstack.org/api-ref/compute/?expanded=list-servers-detail
>
>
>   -Sean
>

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [glance] Last store and client releases for Newton

2016-08-15 Thread Nikhil Komawar

Hi all,


It's that time in the release cycle when we need to wrap things up. The
non-client libraries are lined up to be released for final version in
R-6 and the client one along with n-3 in R-5.


However, these libraries need some time to be tested in gate and for us
to determine a stable version for a release. So, I request any
outstanding patches against the same to be completed as soon as
possible. We will be releasing a final release (most likely) for both
store and client in this week (i.e. in R-7). This gives us some time to
identify bugs associated and address them prompty without having to rush
at the last minute.


Thanks for your co-operation.


Release schedule: http://releases.openstack.org/newton/schedule.html


-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova][glance] snapshots are broken by default with newton and glance v2

2016-07-27 Thread Nikhil Komawar


Thanks Matt, a very correct and precise assessment on the usage in Nova.

I, however, wanted to point out one thing for the audience -- the v2
Image schemas are discoverable and assert the purpose of setting
operator defined and in most cases operator used protected properties.
This is when the api v2 was designed was considered, having a flat
namespace with schematic validation on the properties that makes it
richer experience for advanced usage. The downside, of course, if what
one sees when having relatively straightforward calls that have similar
assumptions with those of the v1 api.

http://developer.openstack.org/api-ref-image-v2.html#image-schemas-v2


On 7/27/16 4:44 PM, Matt Riedemann wrote:
> On 7/20/2016 7:01 PM, Nikhil Komawar wrote:
>
>> Thanks Matt. The bug looked very descriptive so, I commented my thoughts
>>
>> there https://bugs.launchpad.net/python-glanceclient/+bug/1596602
>>
>>
>>
>> On 7/20/16 4:18 PM, Matt Riedemann wrote:
>>
>>> On 7/18/2016 4:41 AM, Erno Kuvaja wrote:
>>>
>>>> On Mon, Jul 18, 2016 at 5:19 AM, Nikhil Komawar
>>>>
>>>> <nik.koma...@gmail.com> wrote:
>>>>
>>>>> Thanks Matt. I've scheduled for a release of the client this week.
>>>>>
>>>>>
>>>>>
>>>>> On 7/16/16 4:09 AM, Matt Riedemann wrote:
>>>>>
>>>>>> This is more of a heads up than anything.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Our internal CI is running Tempest with images that don't have
>>>>>>
>>>>>> kernel_id or ramdisk_id properties set.
>>>>>>
>>>>>>
>>>>>>
>>>>>> We're running from master so nova defaults to use_glance_v1=False.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Because of this:
>>>>>>
>>>>>>
>>>>>>
>>>>>> https://github.com/openstack/nova/blob/47358449d359a287d21426b4e1f18479a4d1fd36/nova/compute/api.py#L867-L868
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> and this:
>>>>>>
>>>>>>
>>>>>>
>>>>>> https://github.com/openstack/nova/blob/47358449d359a287d21426b4e1f18479a4d1fd36/nova/image/glance.py#L835
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> The snapshot image properties get kernel_id and ramdisk_id set to
>>>>>> None
>>>>>>
>>>>>> since that's what the glance v2 schema requires.
>>>>>>
>>>>>>
>>>>>>
>>>>>> However, python-glanceclient has it's own outdated copy of the schema
>>>>>>
>>>>>> which doesn't allow null values for those properties, see bug:
>>>>>>
>>>>>>
>>>>>>
>>>>>> https://bugs.launchpad.net/python-glanceclient/+bug/1596602
>>>>>>
>>>>>>
>>>>>>
>>>>>> We don't hit this in the community CI because the image that Tempest
>>>>>>
>>>>>> uses from devstack has the kernel_id and ramdisk_id properties set:
>>>>>>
>>>>>>
>>>>>>
>>>>>> http://logs.openstack.org/52/335152/1/check/gate-tempest-dsvm-neutron-src-python-glanceclient/d393db9/logs/devstacklog.txt.gz#_2016-06-28_18_40_12_429
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> But for anyone else upgrading to Newton that has images without those
>>>>>>
>>>>>> properties set and doesn't have use_glance_v1=True in nova.conf is
>>>>>>
>>>>>> going to be broken.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Since we really want to get people off glance v1 and move to
>>>>>>
>>>>>> deprecation in Ocata, we need to get this merged and released:
>>>>>>
>>>>>>
>>>>>>
>>>>>> https://review.openstack.org/#/c/335152/
>>>>>>
&g

Re: [openstack-dev] [glance] [glare] Glance virtual midcycle recordings

2016-07-27 Thread Nikhil Komawar

Thanks Jeremy. The worse part is that we do have to share editable
collab links with the participants and they are out and visible.
Nevertheless, this is nice feature to use and can be useful in some
situations.

And, I was trying to be frivolous on the authorship colors but again
quite useful feature.


On 7/27/16 5:15 PM, Jeremy Stanley wrote:
> On 2016-07-27 13:08:35 -0400 (-0400), Nikhil Komawar wrote:
> [...]
>> There have been some noted instances where people either inadvertently
>> or otherwise have updated the etherpad, thus removing the text. Please
>> be considerate and watchful of your keyboard when keeping the etherpad open.
> Note that you can share read-only URLs to pads (checkbox under the
> "share and embed this pad" dropdown that looks like ), for people
> to use as a reference if they don't intend to make further
> modifications to its content.
>
>> But for the record, here's the content/links that can be accessed if you
>> are not a fan of the etherpad colors.
> [...]
>
> You can also hide the authorship colours in your browser (the
> "settings" dropdown that looks like a gear has a checkbox for that),
> if they're annoying.

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [glance] glance developers and operators midcycle sync -- recordings

2016-07-27 Thread Nikhil Komawar

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
productive discussions for the first time event of such nature. I hope
that we will continue to keep this collaboration going and maintain a
cadence between development and operators.


Thanks to Kris for letting us use a tool that let's recordings possible.
I've managed to trans-code the audio/visual into a youtube video with
the chat transcripts posted as a paste in the description there.


The audio/video recording is available at:
_https://youtu.be/DuSvm92iscM_

Chat transcript available at:   http://paste.openstack.org/show/542469/




Please find the full details of the event including notes on the various
topics at:
https://etherpad.openstack.org/p/newton-glance-and-ops-midcycle-sync


As always, feel free to reach out if any questions or comments. Cheers!

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [glance] [glare] Glance virtual midcycle recordings

2016-07-27 Thread Nikhil Komawar

Hi all,


The Glance virtual midcycle was last month and we were able to record
the event and write meeting notes. Please see the "Recordings" (line 30
now) sub-title for audio/visual updates and meeting notes at the near
bottom of the etherpad linked below.


https://etherpad.openstack.org/p/newton-glance-virtual-midcycle


There have been some noted instances where people either inadvertently
or otherwise have updated the etherpad, thus removing the text. Please
be considerate and watchful of your keyboard when keeping the etherpad open.

But for the record, here's the content/links that can be accessed if you
are not a fan of the etherpad colors.

Recordings:
 
* Day 1 Recording (MP4) (143MB) - Download from
https://dl.dropboxusercontent.com/s/f5syv2d1gyjh8lm/GlanceVirtualMidcycleDay1.mp4
* Day 2 Glance Newton Midcycle Meetup - Glare
API _https://youtu.be/FgbgiaAFGxE_
* Day 2 GlanceSpecs discussionhttps://youtu.be/feiORKFiMI0

More permanent location of the meeting details:
http://paste.openstack.org/show/542667/

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [glance] [glance_store] Removing the S3 driver

2016-07-27 Thread Nikhil Komawar

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 glance_store updates. This was discussed a bit during the
glance-operators sync last month [3] too.


The plan is to release store as soon as this [2] review merges and after
currently proposed glance_store v0.15.0 release is out & tested on
glance gate. For now, the tentative release date with this change is
sometime mid-next-week so that this happens in Newton time-frame.


Either way, I just wanted to give a quick heads up and see if I should
be doing more courtesy additions, doc updates, etc. towards this.
Reviews on the proposal are welcome for the feedback as well.


[1] https://review.openstack.org/#/c/266077/

[2] https://review.openstack.org/#/c/347620/

[3] https://etherpad.openstack.org/p/newton-glance-and-ops-midcycle-sync


Cheers,

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [glance] [oslo] configs help text for glance_store

2016-07-27 Thread Nikhil Komawar

Hi all,


There was a intricate issue [1] when using help text with additive
strings for translations, when passed through oslo.config. The error
could not be seen on your local test environment or on glance_store docs
visibly as it reflected only on glance docs gate. (Well, unless you
tested the latest of glance_store with glance before commit/review.)


Thanks to Doug Hellmann, a solution for this has been proposed [2] for
that issue. However, until the next release and subsequent sync of
oslo.config in glance, I sincerely advice all the glance core reviews,
glance_store driver maintainers and all other respective individuals to
refrain from merging any help texts that have such 'additive strings'.


This may have an adverse effect on the glance gate and on further
releases of glance_store in Newton in this release critical period.
Also, note that the 0.14.0 release of glance_store had to be pinned down
[3] [4] and I've proposed a short release for the store lib 0.15.0 [5]
that will help us evaluate store ;  propose  & review changes therein in
a informed manner.


For those working on improving help text, I request you to test your
latest changes the way Doug has described testing oslo.config change in
a comment on PS1 here [2]. Please leave a comment on your review once
you have tested your config help text changes as such and help the
reviewers save time by allowing them to 'not' do the same locally for
every help text change proposed.


Hope that the severity of the issue, message and intent is clear to all
the audience concerned. If not, please feel free to reach out. Let's all
make sure we progress through the review queue in the most important
phase of the release cycle.


[1] https://bugs.launchpad.net/oslo.config/+bug/1605648

[2] https://review.openstack.org/#/c/347907/

[3] https://bugs.launchpad.net/glance-store/+bug/1606746

[4]
http://lists.openstack.org/pipermail/openstack-docs/2016-July/008910.html

[5] https://review.openstack.org/#/c/347621/

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Glare][Heat][Tacker][Murano][App-Catalog] [Glance] How to validate your binary data in OpenStack

2016-07-25 Thread Nikhil Komawar

Thanks for your nice message Mikhail.


I, however, wanted to address a small correction to avoid any further
presumptions about Glare, Glance and Images API with the tags associated
in the email subject herewith. (also adding Glance tag to the list to
ensure we reach the appropriate Images related audience).


On 7/25/16 2:26 PM, Mikhail Fedosin wrote:
> Hello! Today I want to discuss with community one good feature in
> Glare - artifact validation. In short Glare allows to validate binary
> data before it's uploaded to store. For example, for Tosca we're able
> to check if uploaded yaml is a valid template [1], for vm images we
> can test their integrity. For sure, Glare supports quite sophisticated
> workflows, like sending murano packages to external CI
While this feature looks nothing less than excellent, it is unfortunate
that the Images API is built into Glance -- meaning Glance will remain
the reference implementation of the OpenStack Images API for the near to
long future. So, while it may be possible to test integrity of data
assets, it won't be possible for any operator/user/API-consumer to use
Glare for Images as Glance will remain the whole and sole API for Images
and all future features need to be implemented therein.

The reasons for this have been discussed briefly in the proposal
(review) of the Glare spec and in related conversations. If anyone needs
more info, please reach out.

> or validate Heat templates with given environments. 
>
> So, I want to think out what validation is exactly required from Glare
> and how we can help related projects to succeed, checking and reliably
> storing their binary assets.
>
> Best regards,
> Mikhail Fedosin
>
> [1]
> https://review.openstack.org/#/c/337633/10/contrib/glare/openstack_app_catalog/artifacts.py@159
>
>
>
>
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all][summit] Responding to questions on submitted summit talk?

2016-07-25 Thread Nikhil Komawar

I think this may be the wrong place to ask such info because all the
process on summit presentation is being handled by folks who are not
necessarily openstack developers.

Please follow:
https://www.openstack.org/summit/barcelona-2016/call-for-presentations/selection-process
and send email to summit [at] openstack [dot] org
 as required.

On 7/25/16 10:55 AM, Ben Nemec wrote:
> Hi,
>
> I got a question from one of the track chairs on my presentation, but
> the email came from a noreply address and I don't see anywhere on the
> submission page that I can respond to feedback.  How are we supposed to
> do that?
>
> Thanks.
>
> -Ben
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-- 

Thanks,
Nikhil

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [glance] [docs] WADL migration achieved

2016-07-23 Thread Nikhil Komawar

Hi all,


I wanted to share my rejoice with you all that after persistent effort
from Brian Rosmaita, we've (Glance) managed to accomplish another
priority for this cycle the WADL migration, along with a good number of
updates to the api-ref docs. For those unaware, this was the request
from the docs team at the beginning of newton release [1].


Kudos Brian and everyone else who have pitched into this effort
including reviews. Please consider my congratulations to all involved
for this nice change.


[1]
http://lists.openstack.org/pipermail/openstack-dev/2016-May/thread.html#93765

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova][glance] snapshots are broken by default with newton and glance v2

2016-07-20 Thread Nikhil Komawar

Thanks Matt. The bug looked very descriptive so, I commented my thoughts
there https://bugs.launchpad.net/python-glanceclient/+bug/1596602

On 7/20/16 4:18 PM, Matt Riedemann wrote:
> On 7/18/2016 4:41 AM, Erno Kuvaja wrote:
>> On Mon, Jul 18, 2016 at 5:19 AM, Nikhil Komawar
>> <nik.koma...@gmail.com> wrote:
>>> Thanks Matt. I've scheduled for a release of the client this week.
>>>
>>> On 7/16/16 4:09 AM, Matt Riedemann wrote:
>>>> This is more of a heads up than anything.
>>>>
>>>> Our internal CI is running Tempest with images that don't have
>>>> kernel_id or ramdisk_id properties set.
>>>>
>>>> We're running from master so nova defaults to use_glance_v1=False.
>>>>
>>>> Because of this:
>>>>
>>>> https://github.com/openstack/nova/blob/47358449d359a287d21426b4e1f18479a4d1fd36/nova/compute/api.py#L867-L868
>>>>
>>>>
>>>>
>>>> and this:
>>>>
>>>> https://github.com/openstack/nova/blob/47358449d359a287d21426b4e1f18479a4d1fd36/nova/image/glance.py#L835
>>>>
>>>>
>>>>
>>>> The snapshot image properties get kernel_id and ramdisk_id set to None
>>>> since that's what the glance v2 schema requires.
>>>>
>>>> However, python-glanceclient has it's own outdated copy of the schema
>>>> which doesn't allow null values for those properties, see bug:
>>>>
>>>> https://bugs.launchpad.net/python-glanceclient/+bug/1596602
>>>>
>>>> We don't hit this in the community CI because the image that Tempest
>>>> uses from devstack has the kernel_id and ramdisk_id properties set:
>>>>
>>>> http://logs.openstack.org/52/335152/1/check/gate-tempest-dsvm-neutron-src-python-glanceclient/d393db9/logs/devstacklog.txt.gz#_2016-06-28_18_40_12_429
>>>>
>>>>
>>>>
>>>> But for anyone else upgrading to Newton that has images without those
>>>> properties set and doesn't have use_glance_v1=True in nova.conf is
>>>> going to be broken.
>>>>
>>>> Since we really want to get people off glance v1 and move to
>>>> deprecation in Ocata, we need to get this merged and released:
>>>>
>>>> https://review.openstack.org/#/c/335152/
>>>>
>>>> And bump the minimum required python-glanceclient in
>>>> global-requirements for Newton.
>>>>
>>>> I'm not really sure why python-glanceclient even has it's own copy of
>>>> the image schema, that seems redundant and error prone given the
>>>> glance API already validates that, but it's kind of beside the point
>>>> right now.
>>>>
>>>
>>> -- 
>>>
>>> Thanks,
>>> Nikhil
>>>
>>>
>>> __
>>>
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>> Hi Matt,
>>
>> Something has broken on the way if that shipped schema actually affect
>> your operation. That should be used _only_ when the client is called
>> without connection to the Glance API (for example in a case you have
>> no env set and you call `glance help`), this is btw the reason why we
>> have that schema shipped with the client.
>>
>> As soon as you execute a call that actually interacts with Glance API
>> we should be pulling the schema from there. So if this is not the
>> case, we've broken somewhere on the way. I'll try to find time to have
>> a look.
>>
>> - Erno
>>
>> __
>>
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
> Yeah I guess the schema fix in glanceclient didn't resolve the issue,
> but I haven't had the time to dig into the bug since we're doing the
> midcycle this week.
>

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [glance] selecting project mascot

2016-07-18 Thread Nikhil Komawar

The etherpad poll has been closed and the votes and the top 3 candidates
in the preferential order have been sent for further evaluation. We will
most likely be selecting one of the 3 candidates mentioned at the near
bottom of the etherpad. More to come once selection has been made.


On 7/12/16 11:24 AM, Nikhil Komawar wrote:
> Hi,
>
>
> Please find this etherpad [1] for helping collaboratively choose Glance
> project mascot. All the information needed to help understand the
> process is in the etherpad.
>
>
> There are quite a few proposals already. Please note the poll closes
> Monday July 18th so please cast your votes as soon as possible.
>
>
> [1] https://etherpad.openstack.org/p/glance-project-mascot
>
>

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova][glance] snapshots are broken by default with newton and glance v2

2016-07-18 Thread Nikhil Komawar

For those needing this release soon, watch out for the announcement.
Ref: https://review.openstack.org/#/c/343708


On 7/18/16 12:19 AM, Nikhil Komawar wrote:
> Thanks Matt. I've scheduled for a release of the client this week.
>
> On 7/16/16 4:09 AM, Matt Riedemann wrote:
>> This is more of a heads up than anything.
>>
>> Our internal CI is running Tempest with images that don't have
>> kernel_id or ramdisk_id properties set.
>>
>> We're running from master so nova defaults to use_glance_v1=False.
>>
>> Because of this:
>>
>> https://github.com/openstack/nova/blob/47358449d359a287d21426b4e1f18479a4d1fd36/nova/compute/api.py#L867-L868
>>
>>
>> and this:
>>
>> https://github.com/openstack/nova/blob/47358449d359a287d21426b4e1f18479a4d1fd36/nova/image/glance.py#L835
>>
>>
>> The snapshot image properties get kernel_id and ramdisk_id set to None
>> since that's what the glance v2 schema requires.
>>
>> However, python-glanceclient has it's own outdated copy of the schema
>> which doesn't allow null values for those properties, see bug:
>>
>> https://bugs.launchpad.net/python-glanceclient/+bug/1596602
>>
>> We don't hit this in the community CI because the image that Tempest
>> uses from devstack has the kernel_id and ramdisk_id properties set:
>>
>> http://logs.openstack.org/52/335152/1/check/gate-tempest-dsvm-neutron-src-python-glanceclient/d393db9/logs/devstacklog.txt.gz#_2016-06-28_18_40_12_429
>>
>>
>> But for anyone else upgrading to Newton that has images without those
>> properties set and doesn't have use_glance_v1=True in nova.conf is
>> going to be broken.
>>
>> Since we really want to get people off glance v1 and move to
>> deprecation in Ocata, we need to get this merged and released:
>>
>> https://review.openstack.org/#/c/335152/
>>
>> And bump the minimum required python-glanceclient in
>> global-requirements for Newton.
>>
>> I'm not really sure why python-glanceclient even has it's own copy of
>> the image schema, that seems redundant and error prone given the
>> glance API already validates that, but it's kind of beside the point
>> right now.
>>

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [nova][glance] snapshots are broken by default with newton and glance v2

2016-07-17 Thread Nikhil Komawar

Thanks Matt. I've scheduled for a release of the client this week.

On 7/16/16 4:09 AM, Matt Riedemann wrote:
> This is more of a heads up than anything.
>
> Our internal CI is running Tempest with images that don't have
> kernel_id or ramdisk_id properties set.
>
> We're running from master so nova defaults to use_glance_v1=False.
>
> Because of this:
>
> https://github.com/openstack/nova/blob/47358449d359a287d21426b4e1f18479a4d1fd36/nova/compute/api.py#L867-L868
>
>
> and this:
>
> https://github.com/openstack/nova/blob/47358449d359a287d21426b4e1f18479a4d1fd36/nova/image/glance.py#L835
>
>
> The snapshot image properties get kernel_id and ramdisk_id set to None
> since that's what the glance v2 schema requires.
>
> However, python-glanceclient has it's own outdated copy of the schema
> which doesn't allow null values for those properties, see bug:
>
> https://bugs.launchpad.net/python-glanceclient/+bug/1596602
>
> We don't hit this in the community CI because the image that Tempest
> uses from devstack has the kernel_id and ramdisk_id properties set:
>
> http://logs.openstack.org/52/335152/1/check/gate-tempest-dsvm-neutron-src-python-glanceclient/d393db9/logs/devstacklog.txt.gz#_2016-06-28_18_40_12_429
>
>
> But for anyone else upgrading to Newton that has images without those
> properties set and doesn't have use_glance_v1=True in nova.conf is
> going to be broken.
>
> Since we really want to get people off glance v1 and move to
> deprecation in Ocata, we need to get this merged and released:
>
> https://review.openstack.org/#/c/335152/
>
> And bump the minimum required python-glanceclient in
> global-requirements for Newton.
>
> I'm not really sure why python-glanceclient even has it's own copy of
> the image schema, that seems redundant and error prone given the
> glance API already validates that, but it's kind of beside the point
> right now.
>

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [glance] selecting project mascot

2016-07-12 Thread Nikhil Komawar

Hi,


Please find this etherpad [1] for helping collaboratively choose Glance
project mascot. All the information needed to help understand the
process is in the etherpad.


There are quite a few proposals already. Please note the poll closes
Monday July 18th so please cast your votes as soon as possible.


[1] https://etherpad.openstack.org/p/glance-project-mascot


-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] Proposal: Architecture Working Group

2016-06-20 Thread Nikhil Komawar

+1 , great idea.

if we can add a mission/objective based on the nice definitions you
added, will help a long way in cross-project architecture evolution.
moreover, I'd like this to be a integration point for openstack projects
(and not a silo) so that we can build the shared understanding we really
need to build.

On 6/17/16 5:52 PM, Clint Byrum wrote:
> ar·chi·tec·ture
> ˈärkəˌtek(t)SHər/
> noun
> noun: architecture
>
> 1. 
>
> the art or practice of designing and constructing buildings.
>
> synonyms:building design, building style, planning, building, 
> construction; 
>
> formalarchitectonics 
>
> "modern architecture"
>
> the style in which a building is designed or constructed, especially with 
> regard to a specific period, place, or culture.
>
> plural noun: architectures
>
> "Victorian architecture"
>
> 2. 
>
> the complex or carefully designed structure of something.
>
> "the chemical architecture of the human brain"
>
> the conceptual structure and logical organization of a computer or 
> computer-based system.
>
> "a client/server architecture"
>
> synonyms:structure, construction, organization, layout, design, build, 
> anatomy, makeup; 
>
> informalsetup 
>
> "the architecture of a computer system"
>
>
> Introduction
> =
>
> OpenStack is a big system. We have debated what it actually is [1],
> and there are even t-shirts to poke fun at the fact that we don't have
> good answers.
>
> But this isn't what any of us wants. We'd like to be able to point
> at something and proudly tell people "This is what we designed and
> implemented."
>
> And for each individual project, that is a possibility. Neutron can
> tell you they designed how their agents and drivers work. Nova can
> tell you that they designed the way conductors handle communication
> with API nodes and compute nodes. But when we start talking about how
> they interact with each other, it's clearly just a coincidental mash of
> de-facto standards and specs that don't help anyone make decisions when
> refactoring or adding on to the system.
>
> Oslo and cross-project initiatives have brought some peace and order
> to the implementation and engineering processes, but not to the design
> process. New ideas still start largely in the project where they are
> needed most, and often conflict with similar decisions and ideas in other
> projects [dlm, taskflow, tooz, service discovery, state machines, glance
> tasks, messaging patterns, database patterns, etc. etc.]. Often times this
> creates a log jam where none of the projects adopt a solution that would
> align with others. Most of the time when things finally come to a head
> these things get done in a piecemeal fashion, where it's half done here,
> 1/3 over there, 1/4 there, and 3/4 over there..., which to the outside
> looks like  chaos, because that's precisely what it is.
>
> And this isn't always a technical design problem. OpenStack, for instance,
> isn't really a micro service architecture. Of course, it might look like
> that in diagrams [2], but we all know it really isn't. The compute node is
> home to agents for every single concern, and the API interactions between
> the services is too tightly woven to consider many of them functional
> without the same lockstep version of other services together. A game to
> play is ask yourself what would happen if a service was isolated on its
> own island, how functional would its API be, if at all. Is this something
> that we want? No. But there doesn't seem to be a place where we can go
> to actually design, discuss, debate, and ratify changes that would help
> us get to the point of gathering the necessary will and capability to
> enact these efforts.
>
> Maybe nova-compute should be isolated from nova, with an API that
> nova, cinder and neutron talk to. Maybe we should make the scheduler
> cross-project aware and capable of scheduling more than just nova
> instances. Maybe we should have experimental groups that can look at how
> some of this functionality could perhaps be delegated to non-openstack
> projects. We hear that Mesos, for example to help with the scheduling
> aspects, but how do we discuss these outside hijacking threads on the
> mailing list? These are things that we all discuss in the hallways
> and bars and parties at the summit, but because they cross projects at
> the design level, and are inherently a lot of social and technical and
> exploratory work, Many of us fear we never get to a place of turning
> our dreams into reality.
>
> So, with that, I'd like to propose the creation of an Architecture Working
> Group. This group's charge would not be design by committee, but a place
> for architects to share their designs and gain support across projects
> to move forward with and ratify architectural decisions. That includes
> coordinating exploratory work that may turn into being the base of further
> architectural decisions for OpenStack. I

Re: [openstack-dev] [glance] Proposal of a virtual mid-cycle instead of the co-located

2016-06-14 Thread Nikhil Komawar

Please note the details on the midcycle event are updated here:
https://wiki.openstack.org/wiki/VirtualSprints#Glance_Virtual_midcycle_sync

We will be using the etherpad (given in the link above) as a live wiki
for central place of updated info.

On 6/8/16 9:52 AM, Nikhil Komawar wrote:
> This event is confirmed, more details will be out soon.
>
>
> On 5/29/16 11:15 PM, Nikhil Komawar wrote:
>> Hello,
>>
>>
>> I would like to propose a two day 4 hour sessions each of Glance virtual
>> mid-cycle on June 15th Wednesday & 16th Thursday, 1400 UTC onward. This
>> is a replacement of the Glance mid-cycle meetup that we've cancelled.
>> Some people have already expressed some items to discuss then and I
>> would like for us to utilize a couple of hours discussing the
>> glance-specs so that we can apply spec-soft-freeze [1] in a better capacity.
>>
>>
>> We can try to accommodate topics according to the TZ, for example topics
>> proposed by folks in EMEA earlier in the day vs. for those in the PDT TZ
>> in the later part of the event.
>>
>>
>> Please vote with +1, 0, -1. If the time/date doesn't work, please
>> propose 2-3 additional slots.
>>
>>
>> We can use either hangouts, bluejeans or an IBM conferencing tool as
>> required, which is to be finalized closer to the event.
>>
>>
>> I will setup an agenda etherpad once we decide on the date/time.
>>
>>
>> [1] http://lists.openstack.org/pipermail/openstack-dev/2016-May/096175.html
>>

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-06-08 Thread Nikhil Komawar


Please note, due to the last minute additions to the RSVP list, we have
changed the tool to be used. Update info can now be found here:
https://etherpad.openstack.org/p/newton-glance-and-ops-midcycle-sync .

Please try to join 5-10 minutes before the meeting as you may have to
install a plugin and give us time to fix any issues you may face.


On 6/7/16 11:51 PM, Nikhil Komawar wrote:
> Hi all,
>
>
> Thanks a ton for the feedback on the time and thanks to Kris for adding
> items to the agenda [1].
>
>
> Just wanted to announce a few things here:
>
>
> The final decision on the time has been made after a lot of discussions.
>
> This event will be on *Thursday June 9th at 1130 UTC* 
>
> Here's [2] how it looks at/near your timezone.
>
>
> It somewhat manages to accommodate people from different (and extremely
> diverse) timezones but if it's too early or too late for you for this
> full *2 hour* sync, please add your interest topics and name against it
> so that we can schedule your items either later or earlier during the
> event. The schedule will be tentative unless significant/enough
> information is provided on time to help set the schedule in advance.
>
>
> I had kept open agenda from the developers' side so that we can
> collaborate better on the pain points of the operators. You are very
> welcome to add items to the etherpad [1].
>
>
> The event has been updated to the Virtual Sprints wiki [3] and the
> details have been added to the etherpad [1] as well. Please feel free to
> reach out to me for any questions.
>
>
> Thanks for the RSVP and see you soon virtually.
>
>
> [1] https://etherpad.openstack.org/p/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:
>> Hey,
>>
>>
>> Thanks for your interest.
>>
>> Sorry about the confusion. Please consider the same time for Thursday
>> June 9th.
>>
>>
>> Thur June 9th proposed time:
>> http://www.timeanddate.com/worldclock/meetingdetails.html?year=2016=6=9=11=0=0=881=196=47=22=157=87=24=78=283
>>
>>
>> Alternate time proposal:
>> http://www.timeanddate.com/worldclock/meetingdetails.html?year=2016=6=9=23=0=0=881=196=47=22=157=87=24=78=283
>>
>>
>> Overall time planner:
>> http://www.timeanddate.com/worldclock/meetingtime.html?iso=20160609=881=196=47=22=157=87=24=78=283
>>
>>
>>
>> It will really depend on who is strongly interested in the discussions.
>> Scheduling with EMEA, Pacific time (US), Australian (esp. Eastern) is
>> quite difficult. If there's strong interest from San Jose, we may have
>> to settle for a rather awkward choice below:
>>
>>
>> http://www.timeanddate.com/worldclock/meetingdetails.html?year=2016=6=9=4=0=0=881=196=47=22=157=87=24=78=283
>>
>>
>>
>> A vote of +1, 0, -1 on these times would help long way.
>>
>>
>> On 5/31/16 4:35 PM, Belmiro Moreira wrote:
>>> Hi Nikhil,
>>> I'm interested in this discussion.
>>>
>>> Initially you were proposing Thursday June 9th, 2016 at 2000UTC.
>>> Are you suggesting to change also the date? Because in the new
>>> 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 of the US
>>> Glancers :-)
>>>
>>>
>>>
>>>
>>>
>>> I request this time which may help the folks in Eastern and Central US
>>>
>>> time.
>>>
>>> 
>>> http://www.timeanddate.com/worldclock/meetingdetails.html?year=2016=6=7=11=0=0=881=196=47=22=157=87=24=78
>>>
>>>
>>>
>>>
>>>
>>> If it still does not work, I may have to poll the folks in EMEA on how
>>>
>>> strong their intentions are for joining this call.  Because
>>> another time
>>>
>>> slot that works for folks in Australia & US might be too inconvenient
>>>
>>> for those in EMEA:
>>>
>>> 
>>> http://www.timeanddate.com/worldclock/meetingdetails.html?year=2016=6=6=23=0=0=

Re: [openstack-dev] [glance] Proposal of a virtual mid-cycle instead of the co-located

2016-06-08 Thread Nikhil Komawar

This event is confirmed, more details will be out soon.


On 5/29/16 11:15 PM, Nikhil Komawar wrote:
> Hello,
>
>
> I would like to propose a two day 4 hour sessions each of Glance virtual
> mid-cycle on June 15th Wednesday & 16th Thursday, 1400 UTC onward. This
> is a replacement of the Glance mid-cycle meetup that we've cancelled.
> Some people have already expressed some items to discuss then and I
> would like for us to utilize a couple of hours discussing the
> glance-specs so that we can apply spec-soft-freeze [1] in a better capacity.
>
>
> We can try to accommodate topics according to the TZ, for example topics
> proposed by folks in EMEA earlier in the day vs. for those in the PDT TZ
> in the later part of the event.
>
>
> Please vote with +1, 0, -1. If the time/date doesn't work, please
> propose 2-3 additional slots.
>
>
> We can use either hangouts, bluejeans or an IBM conferencing tool as
> required, which is to be finalized closer to the event.
>
>
> I will setup an agenda etherpad once we decide on the date/time.
>
>
> [1] http://lists.openstack.org/pipermail/openstack-dev/2016-May/096175.html
>

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-06-07 Thread Nikhil Komawar

Hi all,


Thanks a ton for the feedback on the time and thanks to Kris for adding
items to the agenda [1].


Just wanted to announce a few things here:


The final decision on the time has been made after a lot of discussions.

This event will be on *Thursday June 9th at 1130 UTC* 

Here's [2] how it looks at/near your timezone.


It somewhat manages to accommodate people from different (and extremely
diverse) timezones but if it's too early or too late for you for this
full *2 hour* sync, please add your interest topics and name against it
so that we can schedule your items either later or earlier during the
event. The schedule will be tentative unless significant/enough
information is provided on time to help set the schedule in advance.


I had kept open agenda from the developers' side so that we can
collaborate better on the pain points of the operators. You are very
welcome to add items to the etherpad [1].


The event has been updated to the Virtual Sprints wiki [3] and the
details have been added to the etherpad [1] as well. Please feel free to
reach out to me for any questions.


Thanks for the RSVP and see you soon virtually.


[1] https://etherpad.openstack.org/p/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:
> Hey,
>
>
> Thanks for your interest.
>
> Sorry about the confusion. Please consider the same time for Thursday
> June 9th.
>
>
> Thur June 9th proposed time:
> http://www.timeanddate.com/worldclock/meetingdetails.html?year=2016=6=9=11=0=0=881=196=47=22=157=87=24=78=283
>
>
> Alternate time proposal:
> http://www.timeanddate.com/worldclock/meetingdetails.html?year=2016=6=9=23=0=0=881=196=47=22=157=87=24=78=283
>
>
> Overall time planner:
> http://www.timeanddate.com/worldclock/meetingtime.html?iso=20160609=881=196=47=22=157=87=24=78=283
>
>
>
> It will really depend on who is strongly interested in the discussions.
> Scheduling with EMEA, Pacific time (US), Australian (esp. Eastern) is
> quite difficult. If there's strong interest from San Jose, we may have
> to settle for a rather awkward choice below:
>
>
> http://www.timeanddate.com/worldclock/meetingdetails.html?year=2016=6=9=4=0=0=881=196=47=22=157=87=24=78=283
>
>
>
> A vote of +1, 0, -1 on these times would help long way.
>
>
> On 5/31/16 4:35 PM, Belmiro Moreira wrote:
>> Hi Nikhil,
>> I'm interested in this discussion.
>>
>> Initially you were proposing Thursday June 9th, 2016 at 2000UTC.
>> Are you suggesting to change also the date? Because in the new
>> 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 of the US
>> Glancers :-)
>>
>>
>>
>>
>>
>> I request this time which may help the folks in Eastern and Central US
>>
>> time.
>>
>> 
>> http://www.timeanddate.com/worldclock/meetingdetails.html?year=2016=6=7=11=0=0=881=196=47=22=157=87=24=78
>>
>>
>>
>>
>>
>> If it still does not work, I may have to poll the folks in EMEA on how
>>
>> strong their intentions are for joining this call.  Because
>> another time
>>
>> slot that works for folks in Australia & US might be too inconvenient
>>
>> for those in EMEA:
>>
>> 
>> http://www.timeanddate.com/worldclock/meetingdetails.html?year=2016=6=6=23=0=0=881=196=47=22=157=87=24=78
>>
>>
>>
>>
>>
>> Here's the map of cities that may be involved:
>>
>> 
>> http://www.timeanddate.com/worldclock/meetingtime.html?iso=20160607=881=196=47=22=157=87=24=78
>>
>>
>>
>>
>>
>> Please let me know which ones are possible and we can try to work
>> around
>>
>> the times.
>>
>>
>>
>>
>>
>> On 5/31/16 2:54 AM, Blair Bethwaite wrote:
>>
>> > Hi 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 <

Re: [openstack-dev] [nova][glance][qa] Test plans for glance v2 stack

2016-06-07 Thread Nikhil Komawar



On 6/7/16 4:55 PM, Matt Riedemann wrote:
> I tested the glance v2 stack (glance v1 disabled) using a devstack
> change here:
>
> https://review.openstack.org/#/c/325322/
>
> Now that the changes are merged up through the base nova image proxy
> and the libvirt driver, and we just have hyper-v/xen driver changes
> for that series, we should look at gating on this configuration.
>
> I was originally thinking about adding a new job for this, but it's
> probably better if we just change one of the existing integrated gate
> jobs, like gate-tempest-dsvm-full or gate-tempest-dsvm-neutron-full.
>
> Does anyone have an issue with that? Glance v1 is deprecated and the
> configuration option added to nova (use_glance_v1) defaults to True for 

Just wanted to clarify that Glance v1 isn't deprecated yet but the
process will be started, as soon as Nova's port for glance v1->v2 is done.

> compat but is deprecated, and the Nova team plans to drop it's v1
> proxy code in Ocata. So it seems like changing config to use v2 in the
> gate jobs should be a non-issue. We'd want to keep at least one
> integrated gate job using glance v1 to make sure we don't regress
> anything there in Newton.
>

Overall, sounds like a good plan (and no objections).

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-05-31 Thread Nikhil Komawar

Hey,


Thanks for your interest.

Sorry about the confusion. Please consider the same time for Thursday
June 9th.


Thur June 9th proposed time:
http://www.timeanddate.com/worldclock/meetingdetails.html?year=2016=6=9=11=0=0=881=196=47=22=157=87=24=78=283


Alternate time proposal:
http://www.timeanddate.com/worldclock/meetingdetails.html?year=2016=6=9=23=0=0=881=196=47=22=157=87=24=78=283


Overall time planner:
http://www.timeanddate.com/worldclock/meetingtime.html?iso=20160609=881=196=47=22=157=87=24=78=283



It will really depend on who is strongly interested in the discussions.
Scheduling with EMEA, Pacific time (US), Australian (esp. Eastern) is
quite difficult. If there's strong interest from San Jose, we may have
to settle for a rather awkward choice below:


http://www.timeanddate.com/worldclock/meetingdetails.html?year=2016=6=9=4=0=0=881=196=47=22=157=87=24=78=283



A vote of +1, 0, -1 on these times would help long way.


On 5/31/16 4:35 PM, Belmiro Moreira wrote:
> Hi Nikhil,
> I'm interested in this discussion.
>
> Initially you were proposing Thursday June 9th, 2016 at 2000UTC.
> Are you suggesting to change also the date? Because in the new
> 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 of the US
> Glancers :-)
>
>
>
>
>
> I request this time which may help the folks in Eastern and Central US
>
> time.
>
> 
> http://www.timeanddate.com/worldclock/meetingdetails.html?year=2016=6=7=11=0=0=881=196=47=22=157=87=24=78
>
>
>
>
>
> If it still does not work, I may have to poll the folks in EMEA on how
>
> strong their intentions are for joining this call.  Because
> another time
>
> slot that works for folks in Australia & US might be too inconvenient
>
> for those in EMEA:
>
> 
> http://www.timeanddate.com/worldclock/meetingdetails.html?year=2016=6=6=23=0=0=881=196=47=22=157=87=24=78
>
>
>
>
>
> Here's the map of cities that may be involved:
>
> 
> http://www.timeanddate.com/worldclock/meetingtime.html?iso=20160607=881=196=47=22=157=87=24=78
>
>
>
>
>
> Please let me know which ones are possible and we can try to work
> around
>
> the times.
>
>
>
>
>
> On 5/31/16 2:54 AM, Blair Bethwaite wrote:
>
> > Hi 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
> <mailto:nik.koma...@gmail.com>> 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 12:59 AM, Sam Morrison wrote:
>
> >>> I’m hoping some people 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 <mailto:nik.koma...@gmail.com>> wrote:
>
> >>>>
>
> >>>> Hello,
>
> >>>>
>
> >>>>
>
> >>>> Firstly, I would like to thank Fei Long for bringing up a few
> operator
>
> >>>> centric issues to the Glance team. After chatting with him on
> IRC, we
>
> >>>> realized that there may be more operators who would want to
> contribute
>
> >>>> to the discussions to help us take some informed decisions.
>
> >>>>
>
> >>>>
>
> >>>> So, I would like to call for a 2 hour sync for the Glance
> team along
>
> >>>> with interested operators on Thursday June 9th, 2016 at 2000UTC.
>
> >>>>
>
> >>>>
>
> >>>> If you are interested in participating please RSVP here [1], and
>
> &

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

2016-05-31 Thread Nikhil Komawar

Hey,


Thanks for the feedback. 0800UTC is 4am EDT for some of the US Glancers :-)


I request this time which may help the folks in Eastern and Central US
time.
http://www.timeanddate.com/worldclock/meetingdetails.html?year=2016=6=7=11=0=0=881=196=47=22=157=87=24=78


If it still does not work, I may have to poll the folks in EMEA on how
strong their intentions are for joining this call.  Because another time
slot that works for folks in Australia & US might be too inconvenient
for those in EMEA:
http://www.timeanddate.com/worldclock/meetingdetails.html?year=2016=6=6=23=0=0=881=196=47=22=157=87=24=78


Here's the map of cities that may be involved:
http://www.timeanddate.com/worldclock/meetingtime.html?iso=20160607=881=196=47=22=157=87=24=78


Please let me know which ones are possible and we can try to work around
the times.


On 5/31/16 2:54 AM, Blair Bethwaite wrote:
> Hi 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 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 12:59 AM, Sam Morrison wrote:
>>> I’m hoping some people 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,
>>>>
>>>>
>>>> Firstly, I would like to thank Fei Long for bringing up a few operator
>>>> centric issues to the Glance team. After chatting with him on IRC, we
>>>> realized that there may be more operators who would want to contribute
>>>> to the discussions to help us take some informed decisions.
>>>>
>>>>
>>>> So, I would like to call for a 2 hour sync for the Glance team along
>>>> with interested operators on Thursday June 9th, 2016 at 2000UTC.
>>>>
>>>>
>>>> If you are interested in participating please RSVP here [1], and
>>>> participate in the poll for the tool you'd prefer. I've also added a
>>>> section for Topics and provided a template to document the issues clearly.
>>>>
>>>>
>>>> Please be mindful of everyone's time and if you are proposing issue(s)
>>>> to be discussed, come prepared with well documented & referenced topic(s).
>>>>
>>>>
>>>> If you've feedback that you are not sure if appropriate for the
>>>> etherpad, you can reach me on irc (nick: nikhil).
>>>>
>>>>
>>>> [1] https://etherpad.openstack.org/p/newton-glance-and-ops-midcycle-sync
>>>>
>>>> --
>>>>
>>>> Thanks,
>>>> Nikhil Komawar
>>>> Newton PTL for OpenStack Glance
>>>>
>>>>
>>>> __
>>>> OpenStack Development Mailing List (not for usage questions)
>>>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> --
>>
>> Thanks,
>> Nikhil
>>
>>
>> ___
>> OpenStack-operators mailing list
>> openstack-operat...@lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [glance] Focus for week R-18 May 30-June 03

2016-05-30 Thread Nikhil Komawar

Hi all,

Thanks for the feedback offline and indicating that I need to clear my
intent on why this email was sent.

This email was intended primarily to the Glance team to know more about
what the release plans look like as not everyone is able to attend the
meetings and it's near to impossible to keep everyone in the loop,
ad-hoc, on when I intend to work on release stuff.

I guess, I should have mentioned that I am putting my release-liaison
hat on, for establishing the awareness tone of this email. It wasn't a
directive to the team rather a call for partnership to adhere to the
timeline proposed. The purpose is -- People are welcome to contribute
but are not forced to do so; at the same time people may want to know
about the dates to target their bugs/reviews accordingly and help
prioritize the work. Also, as reviews are merged the gate may sometimes
become unstable where the team will benefit from knowing that such
possibility is at hand and something to watch out for.

Part of this email specific to the releases was from 'a release liaison
role'  and I do apologize for missing out on adding that info in the
email. It is more of a plan for me that other are welcome to join in and
all non-mandatory help on this front is greatly appreciated.

May be the title also can be changed a bit to indicate that it is a
awareness and focus email that indicates focus of subset of individuals
(of course, OpenStack is a community so great number of things are
non-mandatory :-) ).

I am sorry if this has been hurtful to some.

On 5/29/16 9:50 PM, Nikhil Komawar wrote:
> Hi team,
>
>
> The focus for week R-18 is as follows:
>
>
> * Mon, part of Tues: Reviews that look good enough to be merged and
> suitable for newton-1 release, any reviews that help fixing important
> bugs or those that possibly need further testing later in the release.
> Please keep any eye on the gate to ensure things are in place. I plan to
> propose a review for newton-1 release tag (a bit early) on Tuesday May
> 31st. Last few days, I have pushed quite a few reviews that looked clear
> enough to be merged. Now, we need to merge reviews (if there are any)
> that people are motivated enough to get them ready for newton-1.
>
> * rest of Tues, Wed: Reviews that help us get a good store and client
> release. As discussed in the meeting [1], I plan to 'propose' a store
> and a client release tag later in the week (possibly on late Wednesday
> or on Thursday). I want Glance team to be ready from the release
> perspective, the actual release will happen whenever release team gets a
> chance; given R-18 is general release week, they look less likely then.
>
> * Fri: Reviews on glance-specs, see if the author has followed up on
> your comments, see which reviews look important to give a early
> indication to the author that the spec is not likely to be accepted for
> Newton if we do not deem it fit during our discussions at
> spec-soft-freeze of June 17, R-16 [2].
>
>
> Please be mindful that Monday May 30th is a federal holiday [3] in the US so 
> you may see folks (across OpenStack) OOO. However, I will be available on 
> Monday.
>
>
> Reference for the week numbers:
> http://releases.openstack.org/newton/schedule.html
>
>
> (unlike some of my emails meant to be notices, this email is okay for 
> discussion)
>
>
> As always, feel free to reach out for any questions or concerns.
>
>
> [1] 
> http://eavesdrop.openstack.org/meetings/glance/2016/glance.2016-05-26-14.03.log.html#l-88
> [2] http://lists.openstack.org/pipermail/openstack-dev/2016-May/094780.html
> [3] https://en.wikipedia.org/wiki/Memorial_Day
>
>
>

-- 

Thanks,
Nikhil

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [glance] [stable] Proposal to add Ian Cordasco to glance-stable-maint

2016-05-30 Thread Nikhil Komawar

This has been done.


Thanks!


On 5/25/16 5:12 PM, Nikhil Komawar wrote:
> Hi all,
>
>
> I would like to propose adding Ian to glance-stable-maint team. The
> interest is coming from him and I've already asked for feedback from the
> current glance-stable-maint folks, which has been in Ian's favor. Also,
> as Ian mentions the current global stable team isn't going to subsume
> the per-project teams anytime soon.
>
>
> Ian is willing to shoulder the responsibility of stable liaison for
> Glance [1] which is great news. If no objections are raised by Friday
> May 27th 2359UTC, we will go ahead and do the respective changes.
>
>
> [1] https://wiki.openstack.org/wiki/CrossProjectLiaisons#Stable_Branch
>
>

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [glance] Proposal of a virtual mid-cycle instead of the co-located

2016-05-29 Thread Nikhil Komawar

Hello,


I would like to propose a two day 4 hour sessions each of Glance virtual
mid-cycle on June 15th Wednesday & 16th Thursday, 1400 UTC onward. This
is a replacement of the Glance mid-cycle meetup that we've cancelled.
Some people have already expressed some items to discuss then and I
would like for us to utilize a couple of hours discussing the
glance-specs so that we can apply spec-soft-freeze [1] in a better capacity.


We can try to accommodate topics according to the TZ, for example topics
proposed by folks in EMEA earlier in the day vs. for those in the PDT TZ
in the later part of the event.


Please vote with +1, 0, -1. If the time/date doesn't work, please
propose 2-3 additional slots.


We can use either hangouts, bluejeans or an IBM conferencing tool as
required, which is to be finalized closer to the event.


I will setup an agenda etherpad once we decide on the date/time.


[1] http://lists.openstack.org/pipermail/openstack-dev/2016-May/096175.html

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-05-29 Thread Nikhil Komawar

Hi Ops team(s),


Can we get some RSVPs on the etherpad to help us plan and coordinate the
event? I'd like to cancel this by June 4th if there isn't significant
interest (less than 3 operator friends).


https://etherpad.openstack.org/p/newton-glance-and-ops-midcycle-sync




On 5/26/16 1:30 AM, 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 12:59 AM, Sam Morrison wrote:
>> I’m hoping some people 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,
>>>
>>>
>>> Firstly, I would like to thank Fei Long for bringing up a few operator
>>> centric issues to the Glance team. After chatting with him on IRC, we
>>> realized that there may be more operators who would want to contribute
>>> to the discussions to help us take some informed decisions.
>>>
>>>
>>> So, I would like to call for a 2 hour sync for the Glance team along
>>> with interested operators on Thursday June 9th, 2016 at 2000UTC. 
>>>
>>>
>>> If you are interested in participating please RSVP here [1], and
>>> participate in the poll for the tool you'd prefer. I've also added a
>>> section for Topics and provided a template to document the issues clearly.
>>>
>>>
>>> Please be mindful of everyone's time and if you are proposing issue(s)
>>> to be discussed, come prepared with well documented & referenced topic(s).
>>>
>>>
>>> If you've feedback that you are not sure if appropriate for the
>>> etherpad, you can reach me on irc (nick: nikhil).
>>>
>>>
>>> [1] https://etherpad.openstack.org/p/newton-glance-and-ops-midcycle-sync
>>>
>>> -- 
>>>
>>> Thanks,
>>> Nikhil Komawar
>>> Newton PTL for OpenStack Glance
>>>
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>



-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [glance] NOTICE: Glance Soft Spec freeze R-16 approaching

2016-05-29 Thread Nikhil Komawar

Hi all,


As stated in my email [1], we will be having the soft spec freeze for
glance-specs on June 17th R-16 [2].


As a part of this freeze we will be evaluating the already proposed
specs for their possibility of getting done in Newton based on the
size/complexity/conflict-of-interest-with-priority/comprehensiveness of
the proposal, author follow-up, the severity of comments, etc. We will
then come up with a list of specs that are likely to make it to Newton
and keep our core reviewers' focus on those. We will then ask other
specs to be proposed against Ocata or later.


This also means that we will not allow new specs to be proposed against
Newton.


This freeze does not apply to lite-specs.


Some of the important factors that will go into this evaluation:

* Core reviewer's bandwidth

* Priorities and focus/interest of those core reviewers involved therein

* Interest shown by the cores on your spec

* Other dependencies involving your proposal -- for example if you are
proposing adding a store driver to glance_store, is there a maintainer
ready to be signed-up, if another spec or lite-spec has overlap or
conflict with your, etc.

* Other important factors raised by cores on the spec or during R-16



I urge all the authors/committers to pay close attention to this
deadline as it will severely affect your plans to propose anything
against Newton if it does not make it in this soft-freeze. If you have
questions or are looking for more help, you are welcome to join us
during one of our glance weekly meetings [3] or reach out to one or more
of the current glance-cores [4].


Please DO NOT ask for reviews on ML or during the meetings, all that
space and time is reserved for project discussions. You are welcome to
use normal media of communication like irc pings, direct emails, etc.
for review requests but not the public channels.


As always, feel free to reach out for any questions or concerns.


[1] http://lists.openstack.org/pipermail/openstack-dev/2016-May/094780.html

[2] http://releases.openstack.org/newton/schedule.html

[3] http://eavesdrop.openstack.org/#Glance_Team_Meeting

[4] http://lists.openstack.org/pipermail/openstack-dev/2016-May/094221.html


-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [glance] Focus for week R-18 May 30-June 03

2016-05-29 Thread Nikhil Komawar

Hi team,


The focus for week R-18 is as follows:


* Mon, part of Tues: Reviews that look good enough to be merged and
suitable for newton-1 release, any reviews that help fixing important
bugs or those that possibly need further testing later in the release.
Please keep any eye on the gate to ensure things are in place. I plan to
propose a review for newton-1 release tag (a bit early) on Tuesday May
31st. Last few days, I have pushed quite a few reviews that looked clear
enough to be merged. Now, we need to merge reviews (if there are any)
that people are motivated enough to get them ready for newton-1.

* rest of Tues, Wed: Reviews that help us get a good store and client
release. As discussed in the meeting [1], I plan to 'propose' a store
and a client release tag later in the week (possibly on late Wednesday
or on Thursday). I want Glance team to be ready from the release
perspective, the actual release will happen whenever release team gets a
chance; given R-18 is general release week, they look less likely then.

* Fri: Reviews on glance-specs, see if the author has followed up on
your comments, see which reviews look important to give a early
indication to the author that the spec is not likely to be accepted for
Newton if we do not deem it fit during our discussions at
spec-soft-freeze of June 17, R-16 [2].


Please be mindful that Monday May 30th is a federal holiday [3] in the US so 
you may see folks (across OpenStack) OOO. However, I will be available on 
Monday.


Reference for the week numbers:
http://releases.openstack.org/newton/schedule.html


(unlike some of my emails meant to be notices, this email is okay for 
discussion)


As always, feel free to reach out for any questions or concerns.


[1] 
http://eavesdrop.openstack.org/meetings/glance/2016/glance.2016-05-26-14.03.log.html#l-88
[2] http://lists.openstack.org/pipermail/openstack-dev/2016-May/094780.html
[3] https://en.wikipedia.org/wiki/Memorial_Day

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-05-25 Thread Nikhil Komawar

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 12:59 AM, Sam Morrison wrote:
> I’m hoping some people 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,
>>
>>
>> Firstly, I would like to thank Fei Long for bringing up a few operator
>> centric issues to the Glance team. After chatting with him on IRC, we
>> realized that there may be more operators who would want to contribute
>> to the discussions to help us take some informed decisions.
>>
>>
>> So, I would like to call for a 2 hour sync for the Glance team along
>> with interested operators on Thursday June 9th, 2016 at 2000UTC. 
>>
>>
>> If you are interested in participating please RSVP here [1], and
>> participate in the poll for the tool you'd prefer. I've also added a
>> section for Topics and provided a template to document the issues clearly.
>>
>>
>> Please be mindful of everyone's time and if you are proposing issue(s)
>> to be discussed, come prepared with well documented & referenced topic(s).
>>
>>
>> If you've feedback that you are not sure if appropriate for the
>> etherpad, you can reach me on irc (nick: nikhil).
>>
>>
>> [1] https://etherpad.openstack.org/p/newton-glance-and-ops-midcycle-sync
>>
>> -- 
>>
>> Thanks,
>> Nikhil Komawar
>> Newton PTL for OpenStack Glance
>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [glance] [defcore] [interop] Proposal for a virtual sync dedicated to Import Refactor May 26th

2016-05-25 Thread Nikhil Komawar

The agenda is up
https://etherpad.openstack.org/p/newton-glance-import-refactor-midcycle-sync-1


Please note
https://wiki.openstack.org/wiki/VirtualSprints#Image_Import_Refactor_Sync_.231_--_Newton


If you are having issues connecting the hangout, you can reach out to me
on IRC at around 1505UTC tomorrow (Thursday May 26).


On 5/20/16 6:00 PM, Nikhil Komawar wrote:
> Hello all,
>
>
> I want to propose having a dedicated virtual sync next week Thursday May
> 26th at 1500UTC for one hour on the Import Refactor work [1] ongoing in
> Glance. We are making a few updates to the spec; so it would be good to
> have everyone on the same page and soon start merging those spec changes.
>
>
> Also, I would like for this sync to be cross project one so that all the
> different stakeholders are aware of the updates to this work even if you
> just want to listen in.
>
>
> Please vote with +1, 0, -1. Also, if the time doesn't work please
> propose 2-3 additional time slots.
>
>
> We can decide later on the tool and I will setup agenda if we have
> enough interest.
>
>
> [1]
> http://specs.openstack.org/openstack/glance-specs/specs/mitaka/approved/image-import/image-import-refactor.html
>
>

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [glance] [stable] Proposal to add Ian Cordasco to glance-stable-maint

2016-05-25 Thread Nikhil Komawar

Hi all,


I would like to propose adding Ian to glance-stable-maint team. The
interest is coming from him and I've already asked for feedback from the
current glance-stable-maint folks, which has been in Ian's favor. Also,
as Ian mentions the current global stable team isn't going to subsume
the per-project teams anytime soon.


Ian is willing to shoulder the responsibility of stable liaison for
Glance [1] which is great news. If no objections are raised by Friday
May 27th 2359UTC, we will go ahead and do the respective changes.


[1] https://wiki.openstack.org/wiki/CrossProjectLiaisons#Stable_Branch


-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

2016-05-25 Thread Nikhil Komawar

Hello,


Firstly, I would like to thank Fei Long for bringing up a few operator
centric issues to the Glance team. After chatting with him on IRC, we
realized that there may be more operators who would want to contribute
to the discussions to help us take some informed decisions.


So, I would like to call for a 2 hour sync for the Glance team along
with interested operators on Thursday June 9th, 2016 at 2000UTC. 


If you are interested in participating please RSVP here [1], and
participate in the poll for the tool you'd prefer. I've also added a
section for Topics and provided a template to document the issues clearly.


Please be mindful of everyone's time and if you are proposing issue(s)
to be discussed, come prepared with well documented & referenced topic(s).


If you've feedback that you are not sure if appropriate for the
etherpad, you can reach me on irc (nick: nikhil).


[1] https://etherpad.openstack.org/p/newton-glance-and-ops-midcycle-sync

-- 

Thanks,
Nikhil Komawar
Newton PTL for OpenStack Glance


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [glance] [defcore] [interop] Proposal for a virtual sync dedicated to Import Refactor May 26th

2016-05-25 Thread Nikhil Komawar

Yes, downside indeed.

We will rely on community being civil about this and me kicking people
out for those who did not care to RSVP (if we need free slots).

On 5/25/16 10:24 AM, Flavio Percoco wrote:
> On 25/05/16 09:53 -0400, Nikhil Komawar wrote:
>> Thanks Flavio, Erno.
>>
>> Right now we've 10 participants who have RSVP yes. I was waiting for
>> last min additions but I think we can close the RSVP.
>>
>> We should go for a google hangout on air that can be streamed live on
>> youtube for those merely interested in listening. For all the 10 spots,
>> we can accommodate on the hangout for participation.
>>
>> Here's the link for the event:
>> https://plus.google.com/events/cb4acoebucn25vu8f7enprp85j4
>>
>> More info:
>> https://wiki.openstack.org/wiki/VirtualSprints#Image_Import_Refactor_Sync_.231_--_Newton
>>
>
> Works for me!
>
> The downside of this is that any late addition might be left out as
> the limit of
> participants is 10. Also, if the late addition comes in before any of
> the people
> that had +1'd then the latter would be left out.
>
> I'll be there on time :D
> Flavio
>
>> On 5/25/16 8:51 AM, Erno Kuvaja wrote:
>>>
>>>
>>> On Wed, May 25, 2016 at 12:54 PM, Flavio Percoco <fla...@redhat.com
>>> <mailto:fla...@redhat.com>> wrote:
>>>
>>> On 20/05/16 18:00 -0400, Nikhil Komawar wrote:
>>>
>>> Hello all,
>>>
>>>
>>> I want to propose having a dedicated virtual sync next week
>>> Thursday May
>>> 26th at 1500UTC for one hour on the Import Refactor work [1]
>>> ongoing in
>>> Glance. We are making a few updates to the spec; so it would
>>> be good to
>>> have everyone on the same page and soon start merging those
>>> spec changes.
>>>
>>>
>>> This is tomorrow! Have we decided the tool?
>>>
>>> An invite would be lovely :D
>>>
>>> ++
>>>
>>> Either one of us can provide bluejeans meeting if needed/wanted.
>>>
>>> - Erno
>>>
>>>
>>> Flavio
>>>
>>> --
>>> @flaper87
>>> Flavio Percoco
>>>
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>>
>>> <http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>>
>>>
>>> __
>>>
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>> -- 
>>
>> Thanks,
>> Nikhil
>>
>
>> __
>>
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-- 

Thanks,
Nikhil

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [glance] [defcore] [interop] Proposal for a virtual sync dedicated to Import Refactor May 26th

2016-05-25 Thread Nikhil Komawar

Thanks Flavio, Erno.

Right now we've 10 participants who have RSVP yes. I was waiting for
last min additions but I think we can close the RSVP.

We should go for a google hangout on air that can be streamed live on
youtube for those merely interested in listening. For all the 10 spots,
we can accommodate on the hangout for participation.

Here's the link for the event:
https://plus.google.com/events/cb4acoebucn25vu8f7enprp85j4

More info:
https://wiki.openstack.org/wiki/VirtualSprints#Image_Import_Refactor_Sync_.231_--_Newton

On 5/25/16 8:51 AM, Erno Kuvaja wrote:
>
>
> On Wed, May 25, 2016 at 12:54 PM, Flavio Percoco <fla...@redhat.com
> <mailto:fla...@redhat.com>> wrote:
>
> On 20/05/16 18:00 -0400, Nikhil Komawar wrote:
>
> Hello all,
>
>
> I want to propose having a dedicated virtual sync next week
> Thursday May
> 26th at 1500UTC for one hour on the Import Refactor work [1]
> ongoing in
> Glance. We are making a few updates to the spec; so it would
> be good to
> have everyone on the same page and soon start merging those
> spec changes.
>
>
> This is tomorrow! Have we decided the tool?
>
> An invite would be lovely :D
>
> ++
>
> Either one of us can provide bluejeans meeting if needed/wanted.
>
> - Erno
>  
>
> Flavio
>
> -- 
> @flaper87
> Flavio Percoco
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> <http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-- 

Thanks,
Nikhil

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] when are your mid-cycle meetups?

2016-05-23 Thread Nikhil Komawar



On 5/23/16 5:57 PM, Anita Kuno wrote:
> On 05/23/2016 05:36 PM, Nikhil Komawar wrote:
>> FYI,
>>
>> Glance one was cancelled (so can't put on the wiki), as we are
>> preferring the virtual one for more participation.
>>
>> http://lists.openstack.org/pipermail/openstack-dev/2016-May/095591.html
> Did you add it to the wiki page for virtual sprints?
> https://wiki.openstack.org/wiki/VirtualSprints

idnk. thanks!

>
>> On 5/23/16 5:18 PM, Doug Hellmann wrote:
>>> We are trying to help the organizers of the community bug squash event
>>> choose good dates for their Newton event. We would like to avoid any
>>> sprints or mid-cycles, but there aren't very many listed in the wiki
>>> [1]. If your team is planning an event, please list it so we can do our
>>> best to avoid scheduling conflicts.
>>>
>>> Thanks,
>>> Doug
>>>
>>> [1] https://wiki.openstack.org/wiki/Sprints
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] when are your mid-cycle meetups?

2016-05-23 Thread Nikhil Komawar

FYI,

Glance one was cancelled (so can't put on the wiki), as we are
preferring the virtual one for more participation.

http://lists.openstack.org/pipermail/openstack-dev/2016-May/095591.html

On 5/23/16 5:18 PM, Doug Hellmann wrote:
> We are trying to help the organizers of the community bug squash event
> choose good dates for their Newton event. We would like to avoid any
> sprints or mid-cycles, but there aren't very many listed in the wiki
> [1]. If your team is planning an event, please list it so we can do our
> best to avoid scheduling conflicts.
>
> Thanks,
> Doug
>
> [1] https://wiki.openstack.org/wiki/Sprints
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-- 

Thanks,
Nikhil

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [glance] Unable to set metadata_encryption_key

2016-05-22 Thread Nikhil Komawar

Thanks!

On 5/22/16 8:46 AM, Djimeli Konrad wrote:
> Hello Nikhil,
>
> I have submitted a prototype solution to the problem
> https://review.openstack.org/319659 . I know it is not very exhaustive
> or efficient, but I would like to get your review and option on the issue.
>
> Thanks
> Konrad
>

-- 

Thanks,
Nikhil

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [glance] Focus for week R-19 May 23-27

2016-05-20 Thread Nikhil Komawar

Hi team,


The focus for week R-19 is as follows:


* Mon-Wed: please focus on reviewing specs and lite-specs. Remember the
soft-spec freeze is approaching (R-16), this is when we decide what
specs are likely to be merged in Newton. So, keep reviewing specs. And I
have pointed out to many of your earlier and on ML email that the more
you review, the more likely you are to get reviews. So, keep those
reviews going.


* Thurs-Fri: please focus on anything that is specific to newton-1
release that we'd get released; any important bug, any lite-spec that
we'd target (to see if we can expedite on the process work too), etc.
Our newton-1 target is Tuesday May 31st although the newton-1 general
deadline is Thur Jun 2 in R-18. We need to get reviews merged by Friday
that are intended for newton-1, and the Monday Jun 1 is kept open to
help alleviate last minute issues, additions, etc.


* Help review and provide feedback to any of the process updates I ask
feedback for, as we progress through the week.




Reference for the week numbers:
http://releases.openstack.org/newton/schedule.html


(unlike some of my emails meant to be notices, this email is ok for
discussion)


As always, feel free to reach out for any questions or concerns.

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [glance] Best practices for glance weekly team meetings

2016-05-20 Thread Nikhil Komawar

Hi team,


I have noticed it lately that people were being reluctant on paying
attention to the agenda proposed; either there were too many proposals
or one too many last minute additions. We also did not have any process
to effectively manage the agenda already proposed.  So, as discussed at
this week's team meeting [1], I've added a few best practices about
adding agenda items, to our weekly meeting's etherpad [2] and there's a
bit of protocol to be followed (below). Please note them carefully as I
will be paying close attention to those who do not follow and call them
out if needed.


Please note the following carefully:


* We will be limiting the number of agenda topics per week and there
will be indication in the agenda etherpad about the same.


* Be mindful of others' time, type short precise messages especially
when it comes to updates or review requests.


* Indicate clearly when you are done.


* Try to stay on topic and don't clutter the open discussions, rather
try to propose a topic beforehand.


* Keep focus for the week to stay on track, instead of asking for more
reviews, give reviews that are important for that week. Raise important
questions and discuss findings from that week.


[1]
http://eavesdrop.openstack.org/meetings/glance/2016/glance.2016-05-19-14.00.log.html#l-25

[2] https://etherpad.openstack.org/p/glance-team-meeting-agenda

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [glance] [defcore] [interop] Proposal for a virtual sync dedicated to Import Refactor May 26th

2016-05-20 Thread Nikhil Komawar

Hello all,


I want to propose having a dedicated virtual sync next week Thursday May
26th at 1500UTC for one hour on the Import Refactor work [1] ongoing in
Glance. We are making a few updates to the spec; so it would be good to
have everyone on the same page and soon start merging those spec changes.


Also, I would like for this sync to be cross project one so that all the
different stakeholders are aware of the updates to this work even if you
just want to listen in.


Please vote with +1, 0, -1. Also, if the time doesn't work please
propose 2-3 additional time slots.


We can decide later on the tool and I will setup agenda if we have
enough interest.


[1]
http://specs.openstack.org/openstack/glance-specs/specs/mitaka/approved/image-import/image-import-refactor.html


-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [glance] [VMT] [Security] Proposal to add Brian Rosmaita to the glance-coresec team

2016-05-20 Thread Nikhil Komawar



On 5/20/16 5:23 PM, Jeremy Stanley wrote:
> On 2016-05-20 16:47:50 -0400 (-0400), Nikhil Komawar wrote:
> [...]
>> Please note, however, after talking with Brian and Hemanth, Hemanth has
>> signed up to be Glance liaison to the VMT team along with me. I've
>> updated the wiki:
>> https://wiki.openstack.org/wiki/CrossProjectLiaisons#Vulnerability_management
> [...]
>
> Awesome--thanks! I'm always glad to see more people interested in
> fixing security vulnerabilities in OpenStack.

I do share the sentiment.


-- 

Thanks,
Nikhil

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [glance] [VMT] [security] NOTICE: Current structure of the glance-core-sec team

2016-05-20 Thread Nikhil Komawar

Hi all,


There have been some recent changes to the glance-core-sec team and
liaisons. So, I wanted to send this notice out for people to be aware
and know who to reach out to if they have any issues to discuss.


The current glance-core-sec team includes:

* Brian Rosmaita

* Flavio Percoco

* Hemanth Makkapati

* Kairat Kushaev

* Nikhil Komawar


The current Glance liaisons to the VMT team have been updated here
https://wiki.openstack.org/wiki/CrossProjectLiaisons#Vulnerability_management
.

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [glance] [VMT] [Security] Proposal to add Brian Rosmaita to the glance-coresec team

2016-05-20 Thread Nikhil Komawar



On 5/12/16 5:38 PM, Nikhil Komawar wrote:
> Comments, alternate proposal inline.
>
>
>
> On 5/12/16 8:35 AM, Jeremy Stanley wrote:
>> On 2016-05-11 23:39:58 -0400 (-0400), Nikhil Komawar wrote:
>>> I would like to propose adding add Brian to the team.
>> [...]
>>
>> I'm thrilled to see Glance adding more security-minded reviewers for
>> embargoed vulnerability reports! One thing to keep in mind though is
>> that you need to keep the list of people with access to these
>> relatively small; I see
>> https://launchpad.net/~glance-coresec/+members has five members now.
> Thanks for raising this. Yes, we are worried about it too. But as you
> bring it up, it becomes even more important. A lot of Glancers time
> share with other projects and lack bandwidth to contribute fully to this
> responsibility. Currently, I do not know if anyone can be rotated out as
> we have had pretty good input from all the folks there.
>
>> While the size I picked in item #2 at
>> > https://governance.openstack.org/reference/tags/vulnerability_managed.html#requirements
>>  >
>> is not meant to be a strict limit, you may still want to take this
>> as an opportunity to rotate out some of your less-active reviewers
>> (if there are any).
>>
>>
> Thanks for not being strict on it.
>
> I do however, want to make another proposal:
>
>
> Since Stuart is our VMT liaison and he's on hiatus, can we add Brian as
> his substitute. As soon as Stuart is back and is ready to shoulder this
> responsibility we should do the rotation.


As per the proposal, +1s and no objections raised, I've made the
substitution.

Please note, however, after talking with Brian and Hemanth, Hemanth has
signed up to be Glance liaison to the VMT team along with me. I've
updated the wiki:
https://wiki.openstack.org/wiki/CrossProjectLiaisons#Vulnerability_management


>
> Please vote +1, 0, -1.
>
> I will consider final votes by Thur May 19 2100 UTC.
>

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [glance] NOTICE: Glance midcycle meetup for Newton CANCELLED

2016-05-20 Thread Nikhil Komawar

Hi,


Please note that the Glance midcycle meetup for Newton has been
cancelled as per the agreement [1] at the Glance weekly meeting that
happened Thursday May 19th. The meetup agenda [2] etherpad has been
updated to reflect the same.


Note to wiki moderators: The Sprints wiki [3] has been updated as well.


[1]
http://eavesdrop.openstack.org/meetings/glance/2016/glance.2016-05-19-14.00.log.html#l-131

[2] https://etherpad.openstack.org/p/newton-glance-midcycle-meetup

[3] https://wiki.openstack.org/wiki/Sprints

-- 

Thanks,
Nikhil


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

1 2 3 4 >

1 - 100 of 378 matches

Mail list logo