[openstack-dev] [nova] Nova Bug Team Coordinator for Pike

[Augustina Ragwitz]

As I announced in our last bug team meeting, I will be stepping down
from the Bug Coordinator role. Since taking on the Bug Team Coordinator
role I was laid off from my position where I was able to focus on
upstream Openstack 100% of the time. I've had less time for upstream
Nova work in my new position although I've tried to keep the Bug Team
meetings going and to be a resource for interested folks.

I've appointed Maciej Szankin (macsz on irc) as the new Nova Bug Team
Coordinator for the Pike release. Maciej has been a regular meeting
attendee and bugs team participant. Also he'll be attending the PTG next
week!

Thanks to everyone who attended the bug meetings and has been helping
out!

-- 
Augustina Ragwitz
Señora Software Engineer
---
Waiting for your change to get through the gate? Clean up some Nova
bugs!
http://45.55.105.55:8082/bugs-dashboard.html
---
email: aragwitz+n...@pobox.com
irc: auggy

__
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] [nova][bugs] Nova Bugs Team Meeting this Tuesday

[Augustina Ragwitz]

The next meeting will be Tuesday,  February 7, 2017 at 1800UTC  in
#openstack-meeting-4.

I've updated the meeting agenda:
 https://wiki.openstack.org/wiki/Meetings/Nova/BugsTeam


-- 
Augustina Ragwitz
Señora Software Engineer
---
Waiting for your change to get through the gate? Clean up some Nova
bugs!
http://45.55.105.55:8082/bugs-dashboard.html
---
email: aragwitz+n...@pobox.com
irc: auggy

__
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] [nova][bugs] Nova Bugs Team Meeting this Tuesday Cancelled

[Augustina Ragwitz]

I've had a scheduling conflict and need to cancel the next Nova Bugs
Team meeting. If anyone is interested in running the meeting in my place
since it's been awhile, please feel free to reach out to me via email or
IRC.

-- 
Augustina Ragwitz
Señora Software Engineer
---
Waiting for your change to get through the gate? Clean up some Nova
bugs!
http://45.55.105.55:8082/bugs-dashboard.html
---
email: aragwitz+n...@pobox.com
irc: auggy

__
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] [nova][bugs] Nova Bugs Team Meeting this Tuesday Cancelled

[Augustina Ragwitz]

Due to a scheduling conflict I need to cancel the next Nova Bugs Team
Meeting. The next meeting will be Tuesday,  January 23, 2017 at 1800UTC
in #openstack-meeting-4.

I've updated the meeting agenda:
https://wiki.openstack.org/wiki/Meetings/Nova/BugsTeam


-- 
Augustina Ragwitz
Señora Software Engineer
---
Waiting for your change to get through the gate? Clean up some Nova
bugs!
http://45.55.105.55:8082/bugs-dashboard.html
---
email: aragwitz+n...@pobox.com
irc: auggy

__
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] [nova][bugs] Useful metrics?

[Augustina Ragwitz]

Previously Markus Z. did some great work in putting together a dashboard
we've been using for bug queue maintenance. Are there additional reports
or visualizations of the bug queue that might be interesting or useful
for the team? Is there some information that might make bug skimming,
triaging, or even bug searching easier?

-- 
Augustina Ragwitz
Señora Software Engineer
---
Waiting for your change to get through the gate? Clean up some Nova
bugs!
http://45.55.105.55:8082/bugs-dashboard.html
---
email: aragwitz+n...@pobox.com
irc: auggy

__
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] [nova][bugs] Nova Bugs Team Meeting this Tuesday at 1800 UTC

[Augustina Ragwitz]

The next Nova Bugs Team meeting will be Tuesday, December 13 at 1800UTC
in #openstack-meeting-4

http://www.timeanddate.com/worldclock/fixedtime.html?iso=20161213T18

Feel free to add to the meeting agenda: 
https://wiki.openstack.org/wiki/Meetings/Nova/BugsTeam

-- 
Augustina Ragwitz
Señora Software Engineer
---
Ask me about contributing to OpenStack Nova!
https://wiki.openstack.org/wiki/Nova/Mentoring

Waiting for your change to get through the gate? Clean up some Nova
bugs!
http://45.55.105.55:8082/bugs-dashboard.html
---
email: aragwitz+n...@pobox.com
irc: auggy

__
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] [nova][bugs] Nova Bugs Team Meeting this Tuesday at 1800 UTC

[Augustina Ragwitz]

The next Nova Bugs Team meeting will be Tuesday, November 29 at 1800UTC
in #openstack-meeting-4

http://www.timeanddate.com/worldclock/fixedtime.html?iso=20161129T18

Feel free to add to the meeting agenda: 
https://wiki.openstack.org/wiki/Meetings/Nova/BugsTeam

-- 
Augustina Ragwitz
Señora Software Engineer
---
Ask me about contributing to OpenStack Nova!
https://wiki.openstack.org/wiki/Nova/Mentoring
---
email: aragwitz+n...@pobox.com
irc: auggy

__
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] [nova] Nova Bugs Team Meeting

[Augustina Ragwitz]

Hey folks! I completely mixed up the time due to recent Daylight Savings
time changes and missed the meeting. It also seems I didn't mail out the
meeting reminder. If you have anything you had wanted to bring up,
please reach out to me via email or irc. Otherwise, the next 1800 UTC
meeting will be held on Nov 29th.

-- 
Augustina Ragwitz
Señora Software Engineer
---
Ask me about contributing to OpenStack Nova!
https://wiki.openstack.org/wiki/Nova/Mentoring

Waiting for your change to get through the gate? Clean up some Nova
bugs!
http://45.55.105.55:8082/bugs-dashboard.html
---
email: aragwitz+n...@pobox.com
irc: auggy

__
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] [nova][bugs] No Nova Bugs Team Meeting this Week

[Augustina Ragwitz]

I am unable to host the Bug Team Meeting this week because I'm starting
a new job and will be getting orientated. As usual, if you have bug
related questions, I'm available via email and IRC.

Our next U.S. time meeting will be on November 15, 1800 UTC. While I
don't predict future scheduling conflicts, if anyone is interested in
being a backup to run the U.S. time bugs meeting, please let me know!

-- 
Augustina Ragwitz
Señora Software Engineer
---
Ask me about contributing to OpenStack Nova!
https://wiki.openstack.org/wiki/Nova/Mentoring

Waiting for your change to get through the gate? Clean up some Nova
bugs!
http://45.55.105.55:8082/bugs-dashboard.html
---
email: aragwitz+n...@pobox.com
irc: auggy

__
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] [nova][bugs] No Nova Bugs Team Meeting this Week

[Augustina Ragwitz]

So apparently I did not actually send this to the list. Sorry for any
confusion!

On Mon, Oct 17, 2016, at 01:16 PM, Augustina Ragwitz wrote:
> I'm on holiday and unable to host this week's meeting. If you have any
> questions regarding bug maintenance, bug triage, or anything bug team
> related, feel free to email me, message me in irc (auggy), or just ask
> in #openstack-nova.


-- 
Augustina Ragwitz
Señora Software Engineer
---
Ask me about contributing to OpenStack Nova!
https://wiki.openstack.org/wiki/Nova/Mentoring

Waiting for your change to get through the gate? Clean up some Nova
bugs!
http://45.55.105.55:8082/bugs-dashboard.html
---
email: aragwitz+n...@pobox.com
irc: auggy

__
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] [nova] Nova New Contributor Update

[Augustina Ragwitz]

During the Newton Design Summit the Nova team had a session regarding
new contributor activities
(https://etherpad.openstack.org/p/newton-nova-getting-started). We
agreed that we should update the Mentoring wiki page
(https://wiki.openstack.org/wiki/Nova/Mentoring) with a list of projects
and resources for new folks, and I volunteered to take on the "Mentoring
Czar" role as a result (which I changed to "New Contributor Liaison"). I
moved our "low hanging fruit" etherpad contents over to the Mentoring
wiki and have done my best to keep it current. I also want to thank the
sub-project team members who updated their sections on that wiki page
and I would encourage those who haven't to make sure your contact info
and any newbie-friendly project info is up to date.

During the Newton release cycle, I've spoken with several new
contributors over IRC, via email, and in person. I think we've done a
great job of addressing the need to have someone to provide a first
contact and make suggestions on things to get started on. I'd like to
take this further and continue to follow up with new contributors to
find out what's going well and what they are struggling with. As new
contributors become more established in the community, they may have
some valuable feedback for others looking to get involved that would be
worth capturing. In addition, if new contributors decide not to continue
with Nova, I think it could be valuable to find out why.

Over the past 6 months, I didn't just reach out to new contributors but
I also spoke informally with a few established Nova community members
about their on-boarding experience. The thing I really took away from
these conversations is how helpful it would be for new contributors to
have access to these insights and expectations. In the next few months,
I would like to reach out to established Nova contributors to talk about
their on-boarding experience and what advice they'd give to new
contributors looking to get involved with Nova. Ultimately I'd like to
use these conversations to put together a document for new contributors.
If you would like to participate, please feel free to email me or let me
know on irc (auggy) and I'll add you to my list!

Proposed Nova New Contributor Goals for Ocata:
1) Determine what new contributor/nova onboarding information/feedback
we'd like to collect and how we should collect it
2) Put together a "New Contributor Advice" document based on feedback
from established Nova contributors

I will be at the Barcelona Summit and can add an agenda item to the
Friday Nova Unconference if folks feel it's necessary. I had originally
proposed this as a session but given the amount on Nova's plate for this
super short release, we determined a mailing list post for this would
suffice.

I started a Nova New Contributor brainstorm etherpad for the original
session I'd proposed, feel free to check it out and add any thoughts -
https://etherpad.openstack.org/p/nova-new-contributor-brainstorm

-- 
Augustina Ragwitz
Señora Software Engineer
---
Ask me about contributing to OpenStack Nova!
https://wiki.openstack.org/wiki/Nova/Mentoring

Waiting for your change to get through the gate? Clean up some Nova
bugs!
http://45.55.105.55:8082/bugs-dashboard.html
---
email: aragwitz+n...@pobox.com
irc: auggy

__
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] [nova][bugs] Nova Bugs Team Meeting this Tuesday at 1800 UTC

[Augustina Ragwitz]

The next Nova Bugs Team meeting will be Tuesday, October 3 at 1800 UTC
in #openstack-meeting-4

http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160920T18

Feel free to add to the meeting agenda: 
https://wiki.openstack.org/wiki/Meetings/Nova/BugsTeam

-- 
Augustina Ragwitz
Señora Software Engineer
---
Ask me about contributing to OpenStack Nova!
https://wiki.openstack.org/wiki/Nova/Mentoring

Waiting for your change to get through the gate? Clean up some Nova
bugs!
http://45.55.105.55:8082/bugs-dashboard.html
---
email: aragwitz+n...@pobox.com
irc: auggy

__
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] [nova][bugs] Nova Bugs Team Meeting this Tuesday at 1800 UTC

[Augustina Ragwitz]

The next Nova Bugs Team meeting will be Tuesday, September 20 at 1800
UTC in #openstack-meeting-4

http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160920T18

Feel free to add to the meeting agenda: 
https://wiki.openstack.org/wiki/Meetings/Nova/BugsTeam

-- 
Augustina Ragwitz
Señora Software Engineer
---
Ask me about contributing to OpenStack Nova!
https://wiki.openstack.org/wiki/Nova/Mentoring
---
email: aragwitz+n...@pobox.com
irc: auggy

__
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] Bug team meeting

[Augustina Ragwitz]

Markus discussed the issue with both Timofey and myself, and we agreed
that based on my involvement with the bugs team it made more sense to
have me to take it over. Timofey has agreed to run the 0800 UTC EU
meeting and I'll run the 1800 UTC US/APAC meeting.

As Kashya pointed out, having more timezone coverage is definitely
better, so thanks to Timofey for stepping up!

I also want to acknowledge Sylvain's point regarding RC1 and
regressions. Please make a special effort to watch the bugs queue. Even
if you haven't officially signed up for Bug Skimming Duty, please help
out the team by skimming a bug when you have a little time to spare.  In
particular, keep an eye out for any issues that may have been introduced
in the latest release or for any security related issues. If you have
questions, feel free to ask in #openstack-nova.

* Nova new bugs:
https://bugs.launchpad.net/nova/+bugs?search=Search=New
* Bug Skimming:
https://wiki.openstack.org/wiki/Nova/BugTriage#Weekly_bug_skimming_duty

-- 
Augustina Ragwitz
Señora Software Engineer
---
Ask me about contributing to OpenStack Nova!
https://wiki.openstack.org/wiki/Nova/Mentoring
---
email: aragwitz+n...@pobox.com
irc: auggy

__
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] Bug team meeting

[Augustina Ragwitz]

I should add that I also expressed interest in taking over the Bug Czar
role. I've been actively involved with the bugs team since Markus
revived it earlier this year. I've run meetings when he was unavailable
and also provided assistance to new folks. How is it normally handled if
more than one person is interested in taking on a subteam "czar" type of
role? Should we co-czar?

-- 
Augustina Ragwitz
Señora Software Engineer
---
Ask me about contributing to OpenStack Nova!
https://wiki.openstack.org/wiki/Nova/Mentoring
---
email: aragwitz+n...@pobox.com
irc: auggy

__
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] Bug team meeting

[Augustina Ragwitz]

Hi Timofei,

Based on your post, it sounds like you plan to take over the bug team
meetings? Maybe with Markus stepping down, this could be a good
opportunity to reconsider our meeting schedule. Our meetings are
generally not well attended and I'm not sure if a weekly meeting is
necessary.

Also, the 0800 UTC meeting you mention being cancelled for Sept 13 was
moved to that time from 1000 UTC due to low attendance. Has attendance
improved since that meeting was moved? I don't normally attend it
because it's the middle of the night for me :)

I'm in US Pacific time and it would be very convenient for me to run the
1800 UTC meeting if that's an issue. Alternatively, we could propose a
new time and just have one meeting every other week.

-- 
Augustina Ragwitz
Señora Software Engineer
---
Ask me about contributing to OpenStack Nova!
https://wiki.openstack.org/wiki/Nova/Mentoring
---
email: aragwitz+n...@pobox.com
irc: auggy

__
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] resignation from bug czar role

[Augustina Ragwitz]

It's been great working with you and you've done such a great job with
the bugs team!

I'd be more than happy to pick up the Bug Czar role and continue with
the great work you started.

-- 
Augustina Ragwitz
Señora Software Engineer
---
Ask me about contributing to OpenStack Nova!
https://wiki.openstack.org/wiki/Nova/Mentoring
---
email: aragwitz+n...@pobox.com
irc: auggy

__
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] Nova mascot

[Augustina Ragwitz]

> What will the Foundation do if nova doesn't propose a mascot?

Nothing, I believe.



-- 
Augustina Ragwitz
Señora Software Engineer
---
Ask me about contributing to OpenStack Nova!
https://wiki.openstack.org/wiki/Nova/Mentoring
---
email: aragwitz+n...@pobox.com
irc: auggy

__
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] Nova mascot

[Augustina Ragwitz]

I second the supernova concept. I'm just not a huge fan of an animal.
Unless it's a Tardigrade.

I found some cartoonish things that show a supernova could be
graphically stylized:
* https://heasarc.gsfc.nasa.gov/Images/objects/snrs/SNR_cartoon2.gif
*
http://coffeeshopphysics.com/articles/2011-10/12_standing_on_a_crunchy_star/kapow.png
* http://usscouts.org/advance/Images/Nova.gif




-- 
Augustina Ragwitz
Señora Software Engineer
---
Ask me about contributing to OpenStack Nova!
https://wiki.openstack.org/wiki/Nova/Mentoring
---
email: aragwitz+n...@pobox.com
irc: auggy

__
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] focused review pipeline of bug fix changes?

[Augustina Ragwitz]

I like the idea of having a list because it makes it easy for people to
see what's up for review. Anything that allows people to easily point
and click will increase visibility and participation. I also prefer the
list maintenance be as automagic as possible so the burden doesn't fall
on one or two people and thus risk it getting out of date.

I like #3 but I worry about the comments getting spammy if things are
dropped from and added to the list repeatedly. Would tagging the bugs in
Launchpad work? We can easily remove tags in Launchpad, it's a
query-able list, and the reviewer would immediately have some context.

-- 
Augustina Ragwitz
Señora Software Engineer
---
Ask me about contributing to OpenStack Nova!
https://wiki.openstack.org/wiki/Nova/Mentoring
---
email: aragwitz+n...@pobox.com
irc: auggy

__
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] [PTLs][all][mentoring] Mentors needed in specific technical areas

[Augustina Ragwitz]

 
>> On 12:54 May 24, Augustina Ragwitz wrote:
>> Hi Emily,
>>
>> I'm the Nova Mentoring Czar and we have a Wiki page with a list of
>> projects that would be good for new contributors:
>> https://wiki.openstack.org/wiki/Nova/Mentoring
>>
>> For Nova, I'd encourage potential contributors to get involved with a
>> specific project so that mentoring can happen organically. Interested
>> folks are more than welcome to reach out to me, preferably by email.
>
> There's an assumption here that all projects have things in place
> to begin
> mentoring people. With the people we've spoken to, sometimes just
> reaching on
> IRC gave no answers. This is actually matching people to
> someone who has
> knowledge and is interested/has time to mentor. Even if a match
> can't be made
> right away, communication is made. First impressions with on
> boarding is key.
>
> --
> Mike Perez
 
I'm a little confused by your response. I wasn't making any assumptions
or intending to criticize this mentorship program. I understood that
Emily had highlighted gaps in certain technical areas, of which Nova is
one. In recognition of the challenges faced by new contributors, the
Nova team had a session at the Newton Design Summit where we discussed
ideas on how to address these challenges within our own team. One
outcome of this session is that I volunteered for the role of Mentoring
Czar. When I saw Emily's original post, I thought this information might
be relevant. My intention is to share our resources for new contributors
and present myself as a contact point so this information could be
provided to participants in the mentorship program that don't have
mentors assigned. In fact, if other projects do have things in place for
new contributors, it would probably be helpful if they also provided
this information to the mentorship program.
 
Again, my intention was not to criticize and I think any effort to
encourage new contributors is a good thing. I apologize if my original
response suggested otherwise.
 
--
Augustina Ragwitz
irc: auggy
Augustina Ragwitz
Sr Systems Software Engineer, HPE Cloud
Hewlett Packard Enterprise
---
irc: auggy
 
 
__
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] [PTLs][all][mentoring] Mentors needed in specific technical areas

[Augustina Ragwitz]

Hi Emily,

I'm the Nova Mentoring Czar and we have a Wiki page with a list of
projects that would be good for new contributors:
https://wiki.openstack.org/wiki/Nova/Mentoring

For Nova, I'd encourage potential contributors to get involved with a
specific project so that mentoring can happen organically. Interested
folks are more than welcome to reach out to me, preferably by email.

-- 
Augustina Ragwitz
Sr Systems Software Engineer, HPE Cloud
Hewlett Packard Enterprise
---
irc: auggy

__
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] [api] [senlin] [keystone] [ceilometer] [telemetry] Questions about api-ref launchpad bugs

[Augustina Ragwitz]

 
>
> On Tue, May 10, 2016 at 5:14 AM, Atsushi SAKAI
> <sak...@jp.fujitsu.com> wrote:
> Hello Anne
>
> I have several question when I am reading through etherpad's (in
> progress).
> It would be appreciated to answer these questions.
>
> 1)Should api-ref launchpad **bugs** be moved to each modules
> (like keystone, nova etc)?
> Also, this should be applied to moved one's only or all components?
> (compute, baremetal Ref.2)
>
> Ref.
> https://etherpad.openstack.org/p/austin-docs-newtonplan
> API site bug list cleanup: move specific service API ref bugs to
> project's Launchpad
>
> Ref.2
> http://developer.openstack.org/api-ref/compute/
> http://developer.openstack.org/api-ref/baremetal/
>
> Yes! I definitely got agreement from nova team that they want them.
> Does anyone have a Launchpad script that could help with the bulk
> filter/export? Also, are any teams concerned about taking on their API
> reference bugs? Let's chat.
>
 
I had started work on a tool for filing api-ref bugs for Nova before the
Summit and just haven't had a chance to pick it back up. Anyone is
welcome to fork or submit PR's to fix it up. I was trying to get
Launchpad login to work when I had to halt work on it due to the
upcoming summit. It's still very much a WIP and someone may have
something better out there.
 
https://github.com/missaugustina/nova-api-docs-tracker
 
 
--
Augustina Ragwitz
Sr Systems Software Engineer, HPE Cloud
Hewlett Packard Enterprise
---
irc: auggy
__
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] api-ref sprint today & wed

[Augustina Ragwitz]

Currently it's really hard to tell (at least to me) which files have
patches against them and which don't. I've had to manually make a
spreadsheet because it's not obvious to me, at a glance, from the
current commit messages, and I've accidentally started work on several
files that already have owners. Maybe if people could put the .inc
filename in their commit message, or maybe we could agree on a
consistent commit message for whichever phase we're on, it would be
easier to tell, at a glance from the list, what's already being worked
on. Other suggestions welcome, or if there's another list somewhere I
don't know about, a link to that would be great.

This is the list I'm referring to:
https://review.openstack.org/#/q/project:openstack/nova+file:api-ref+status:open


Thanks!
Augustina


-- 
Augustina Ragwitz
Sr Systems Software Engineer, HPE Cloud
Hewlett Packard Enterprise
---
irc: auggy

__
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] [Keystone][Nova] Any Code Examples of Other Services Using Keystone Policy?

[Augustina Ragwitz]

I'm currently working on the spec for Project ID Validation in Nova
using Keystone. The outcome of the Design Summit Session was that the
Nova service user would use the Keystone policy to establish whether the
requester had access to the project at all to verify the id. I was
wondering if there were any code examples of a non-Keystone service
using the Keystone policy in this way?

Also if I misunderstood something, please feel free to correct me or to
clarify!

Here is the etherpad from the session:
https://etherpad.openstack.org/p/newton-nova-keystone
And here is the current spec: https://review.openstack.org/#/c/294337


-- 
Augustina Ragwitz
Sr Systems Software Engineer, HPE Cloud
Hewlett Packard Enterprise
---
irc: auggy

__
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] Proposing Andrey Kurilin for python-novaclient core

[Augustina Ragwitz]

Do ittt!



-- 
Augustina Ragwitz
Sr Systems Software Engineer, HPE Cloud
Hewlett Packard Enterprise
---
irc: auggy

__
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] Newton midcycle planning

[Augustina Ragwitz]

 
>  In any month of any year, Oregon > San Antonio :P  +1 for Hillsboro
>  again from me, but I'm just a tad biased :)
>
 
I have to agree with Dan here, but then again, I am also a bit biased.
 
--
Augustina Ragwitz
Sr Systems Software Engineer, HPE Cloud
Hewlett Packard Enterprise
---
irc: auggy
__
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] Newton midcycle planning

[Augustina Ragwitz]

On Mon, Apr 11, 2016 at 3:54 PM, Michael Still <mi...@stillhq.com> wrote:
>
> Intel at Hillsboro had expressed an interest in hosting the N mid-cycle
> last release, so they might still be an option? I don't recall any other
> possible hosts in the queue, but its possible I've missed someone.
>
>
I was also thinking about following up with Intel since they just hosted
the Horizon Midcycle. I'm in PDX so I can follow up on that.

---
Augustina Ragwitz
Sr Systems Software Engineer, HPE Cloud
Hewlett Packard Enterprise
---
irc: auggy
__
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] Bug for image_cache_manager refactoring

[Augustina Ragwitz]

Thanks Markus (and Hans)!

---
Augustina Ragwitz
Sr Systems Software Engineer, HPE Cloud
Hewlett Packard Enterprise
---
irc: auggy
__
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] [nova] Bug for image_cache_manager refactoring

[Augustina Ragwitz]

I came across a bug filed back in August [1] that brought up a potential
issue with the image_cache_manager in that the loop for building the
BlockDeviceMappingList has the potential to generate enough messages to
take down nova-conductor. There is a TODO comment in the code that
indicates it needs to be refactored. It looks like there was a fix proposed
that was recently abandoned and the bug has now been relabeled as "New".

Currently there is a comment that we should reassess this bug. Should I go
ahead and mark this bug as confirmed to get it into the Triage pipeline? To
me it seems legit, but maybe someone with more context has a different
opinion?

[1] https://bugs.launchpad.net/nova/+bug/1484847

---
Augustina Ragwitz
Sr Systems Software Engineer, HPE Cloud
Hewlett Packard Enterprise
---
irc: auggy
__
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] [nova][novaclient] Responses for Deletion Events

[Augustina Ragwitz]

There's been some discussion regarding a recent bug [1] where an issue was
reported that no confirmation/success message is received from "nova
agent-delete". This behavior is inconsistent from other novaclient delete
commands which do provide a success message.

There are a two issues that need to be addressed before this behavior can
be patched:

1) What would represent sufficient expected behavior in this deletion case?

A few options have been suggested in the bug; we should probably have
consensus. We should keep in mind the novaclient is due to be deprecated in
the near future, to be replaced by the openstack-client.

The options suggested include providing a simple success response or
supporting different levels of response data with options. For instance,
only show a message if the user specifies --verbose explicitly. novaclient
is not consistent with its "delete" behavior, some calls require --verbose
while others are verbose by default.

2) How does the openstack-client behave for deletions? Should we be
consistent with that in our own client?

I've been digging around in the available documentation for the OpenStack
client and didn't see response types documented. This issue has also not
been addressed in any of the HGI or other high level documentation. I
posted a question in the #openstack-sdks channel to see if anyone knows the
answer to this.

This might be a good opportunity to think about a standard for deletion
responses if one hasn't been defined already.


[1] https://bugs.launchpad.net/python-novaclient/+bug/1557888

---
Augustina Ragwitz
Sr Systems Software Engineer, HPE Cloud
Hewlett Packard Enterprise
---
irc: auggy
__
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] Nova midcycle list of attendees

[Augustina Ragwitz]

Another issue is some people may not want to share where they are 
staying or their arrival/departure details. I also appreciated Paul's 
tactfulness here :) Thanks Paul for putting that page up! I particularly 
appreciate the transportation column as I've heard transit in that area 
is a bit sparse. Now I know who to bug for rides!!


Augustina

On 2016-01-14 15:39, Carl Baldwin wrote:

On Jan 14, 2016 3:43 PM, "Anita Kuno"  wrote:
 >
 > On 01/14/2016 12:38 PM, Murray, Paul (HP Cloud) wrote:
 > > I have created a list of attendees for the Nova midcycle here:
https://wiki.openstack.org/wiki/Sprints/NovaMitakaSprintAttendees [1]
 > >
 > > Obviously I can't put anyone's name on it for privacy reasons.
 >
 > What privacy reasons? Every other project lists attendees either on
a
 > wikipage or an etherpad.
 >
 > I don't know that nova has a privacy clause that is different from
any
 > other project. I don't recall a privacy clause when I registered to
attend.

I took this to mean that Paul did not want to publish the list of
attendees himself when it had not been public already.  In my
experience, every other mid-cycle ether pad or wiki has done
registration publicly to begin with but this one initially took
registration privately and they didn't seem to want to take the whole
list public without consent.  I appreciated Paul's consideration here
and gladly added myself.

Carl

Links:
--
[1] https://wiki.openstack.org/wiki/Sprints/NovaMitakaSprintAttendees

__
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] [nova][bugs] help needed: volunteers for bug skimming (1 week)

[Augustina Ragwitz]

I signed up for the week before the Nova Midcycle meeting. Even though 
I'm still new, I feel capable of at least getting the tags mostly right. 
When I'm not quite sure which tag it would fall under, I search for 
similar bugs and see how they were tagged.


I did have one clarifying question, what exactly are the expectations of 
the bug skimming duty? I assumed it was just tagging bugs to get them 
into the appropriate queues for triaging. Do we also need to confirm the 
bugs once they've been tagged or does that fall under "triage" and not 
"skimming"?


Thanks!
Augustina

__
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][bugs] help needed: volunteers for bug skimming (1 week)

[Augustina Ragwitz]

I think I just answered my own question ;) I looked at the blog post 
Markus provided in another part of this thread and it looks like 
"Skimming Duty" means both tag the bugs and the triaging step of 
confirming them such that they should no longer be in "New" status after 
you've touched them. I was confused because when I was looking at bugs 
in Launchpad, many had been tagged but left as "New" thus my need for 
clarification. Markus' blog post [1] is more clear than than the wiki on 
the triage expectations.


Also, Anthony, you can follow the instructions in Markus' original post. 
Just edit the wiki page and add your name to the table. The best irc 
channel for nova issues is #openstack-nova. You might want to see the 
Nova How to Get Involved document [2].


[1] 
http://markuszoeller.github.io/posts/openstack-bugs/#status-and-contributor-responsibility

[2] http://docs.openstack.org/developer/nova/how_to_get_involved.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

Re: [openstack-dev] [nova][bugs] help needed: volunteers for bug skimming (1 week)

[Augustina Ragwitz]

On 2016-01-08 11:27, Anthony Chow wrote:

There is an URL for the duty:

https://wiki.openstack.org/wiki/Nova/BugTriage#Weekly_bug_skimming_duty
[3]


Right, I read the wiki and it wasn't clear to me. Here's what the wiki 
says:


"Since Nova is such an active project with a high number of incoming bug 
reports, we have a separate process for categorizing bugs and 
distributing the load of triage to a larger group of people."


and

"To help make sure that the triage queue stays under control, the 
following table lists the people that have committed to regularly 
triaging bugs for a given tag."


The term "skimming" implies something done quickly at a surface level 
(like skimming off the fat or skimming a book). So I'm just asking, as 
part of "skimming" duty, are we also confirming the bugs, (confirming 
looks like it falls under the "Triaging" step), or is "skimming" just 
about tagging and getting the bugs into the triaging queues?


Thanks!

Augustina



__
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][bugs] Weekly Status Report

[Augustina Ragwitz]

I totally second that on the low-hanging-fruit tag! And I'm happy to 
help with some of the triaging. I'm still pretty new to Nova so I'm not 
sure how helpful I'll be but it seems like a good task for getting to 
know more about things at least from a high level.


Would bug triaging be a meta low-hanging-fruit item? ;)

On 11/06/2015 12:54 PM, Diana Clarke wrote:

On Fri, Nov 6, 2015 at 11:54 AM, Markus Zoeller  wrote:

below is the first report of bug stats I intend to post weekly.
We discussed it shortly during the Mitaka summit that this report
could be useful to keep the attention of the open bugs at a certain
level. Let me know if you think it's missing something.

Thanks Markus!

On the topic of triaging bugs, I'd love to see more of the Nova bugs
tagged with low-hanging-fruit (when appropriate) for those of us
looking for new-contributor-friendly bugs to work on.

 https://bugs.launchpad.net/nova/+bugs?field.tag=low-hanging-fruit

Thanks again & have a great weekend!

Cheers,

--diana

__
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