Re: [openstack-dev] [tc][election] TC candidacy

2017-10-09 Thread Nicolas Bock

On Mon, Oct 09, 2017 at 02:53:27PM +0200, Colleen Murphy wrote:

I'd like to submit my candidacy for a position on the OpenStack TC.


+1 !!

I think Collen would be an an excellent addition to the TC!


I work at SUSE as a Cloud Developer. I have been involved with OpenStack for
three years, first as a contributor to the Puppet-OpenStack team, then with
the
Infra team, and now as a core reviewer for keystone.

From the beginning I have had a keen interest in onboarding new
contributors and
guiding them to be productive community members. Growing our community
following our recent drop in contributors is one of our biggest challenges.
I also see diversifying our community as intertwined with attracting and
onboarding new members. I have always been impressed with OpenStack's
welcoming
community and inclusivity, but the numbers show that we could be doing
better
on gender diversity[1] and I believe we must continue to build up momentum
in
improving cultural inclusivity.

My work in OpenStack has given me with an understanding of the needs of
operators and deployment tool teams and a desire to support those needs.
Admitting deployment tools into the Big Tent was a great step in closing the
communication gap between core projects and deployers and ultimately lead
to an
improvement in the user experience for operators. Continuing this pattern of
inter-group collaboration is fundamental to making OpenStack better.

I care a lot about OpenStack and I'd like to contribute to its overall
health
and success in any way that I can, and I see serving on the TC as an
excellent
way to do that. Thank you for your consideration.

Colleen Murphy (cmurphy)
https://www.openstack.org/community/members/profile/11727/colleen-murphy
http://stackalytics.com/?release=all_id=krinkle

[1] http://superuser.openstack.org/articles/bitergia-intel-report/



__
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] Self-nomination for PTL in Queens

2017-08-08 Thread Nicolas Bock

On Tue, Aug 08, 2017 at 03:58:20PM -0500, Matt Riedemann wrote:

Hi everyone,

This is my self-nomination to continue running as Nova PTL for the 
Queens cycle.


+1 !

If elected, this would be my fourth term as Nova PTL. While I try to 
continually improve, at this point I have a fairly steady way of doing 
things and most people are probably used to that by now. That's not to 
say it's the best way of doing things, so I'm always open to getting 
feedback on what people would like to see more (or less) of from me.


I really see this as a service role and I'm happy to continue being of 
service for another release, which includes preparing for the PTG and 
Forum, being aware of the schedule and communicating major changes or 
plans to various groups (developers, operators, Foundation staff, 
etc).


I'm also happy to say that I'm fortunate enough to have an employer that
supports me doing this again and the amount of time it takes working 
mostly full time in the community.


As for Queens content, we made a lot of progress again in Pike but 
some things are left undone and that's what I'd like to focus on in 
Queens. Specifically:


- Continue to evolve and solidify Nova's interaction with the Placement
 service, which includes getting the allocations code out of the
 compute service, fully supporting shared storage providers (and
 testing that in the Ceph CI job), and finally adding the nested
 resource providers support which will enable other features like vGPUs
 and other hardware-accelerated configurations.
- Close some gaps in our multi-cell support, mainly related to up-calls
 for reschedules during build and affinity/anti-affinity sanity checks,
 and also work on real multi-cell deployment testing in a multi-node CI
 job.
- Finish the Cinder 3.27 API integration early (before the PTG) so we
 can finally get volume multi-attach support.
- Cleanup the documentation now that it has moved in-tree.

Finally, a personal goal for me is going to be working on helping 
mentor someone into the PTL role for the Rocky release, so if you are 
interested in this role, please reach out.


Thanks for your consideration.

--

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


__
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] [rpm-packaging] ptl for queens

2017-08-04 Thread Nicolas Bock

+1 !

On Fri, Aug 04, 2017 at 10:19:20AM +0200, Thomas Bechtold wrote:

Hi,

I announce my candidacy for the PTL of the Packaging RPM project.

I have been a contributor to various OpenStack projects since Havana and I'm
one of the initial cores of the packaging RPM project. The project goal is
to produce a production-ready set of OpenStack packages for RPM-based systems
(like SLES, RHEL, openSUSE, Fedora, etc.).

As a PTL, I would focus on:

- python3 support. The currently available packages are python2 only.
 Distros are moving to python3 as default so providing python3 packages
 (starting with the libs and clients) should be done now.

- getting more services packaged. We currently have most of the libs
 and clients available but there are a lot of services still missing.

- Improve tooling. There are still things that can be automated when
 new packages are created or available ones updated.


Thanks,
Tom

__
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] [OpenStack-Ansible] Proposing Markos Chandras for osa-core

2017-07-18 Thread Nicolas Bock

On Tue, Jul 18, 2017 at 10:23:46AM +0100, Andy McCrae wrote:

Following on from last week's meeting I'd like to propose Markos (hwoarang)
for OSA core.


+1 !!


Markos has done a lot of good reviews and commits over an extended period
of time, and has shown interest in the project as a whole. (Not to mention
the addition of SUSE support)

We already have quite a few +1's from the meeting itself, but opening up to
everybody who wasn't available at the meeting!

Thanks,
Andy



__
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] [keystone] Colleen Murphy for core

2017-05-02 Thread Nicolas Bock

Congratulations Colleen!

On Tue, May 02, 2017 at 01:15:32PM -0500, Lance Bragstad wrote:

Hey folks,

During today's keystone meeting we added another member to keystone's core
team. For several releases, Colleen's had a profound impact on keystone.
Her reviews are meticulous and of incredible quality. She has no hesitation
to jump into keystone's most confusing realms and as a result has become an
expert on several identity topics like federation and LDAP integration.

I'd like to thank Colleen for all her hard work and upholding the stability
and usability of the project.


Congratulations, Colleen!



__
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][docs] Is anyone interested in being the docs liaison for Nova?

2017-03-02 Thread Nicolas Bock

Hi Matt,

I'd be interested as well. Maybe Zhenyu and I could split this 
role, although I am not a native English speaker either :)


Nick

On Wed, Mar 01, 2017 at 09:45:05AM -0600, Matt Riedemann wrote:

There is a need for a liaison from Nova for the docs team to help with
compute-specific docs in the install guide and various manuals.

For example, we documented placement and cells v2 in the nova devref in
Ocata but instructions on those aren't in the install guide, so the docs
team is adding that here [1].

I'm not entirely sure what the docs liaison role consists of, but I
assume it at least means attending docs meetings, helping to review docs
patches that are related to nova, helping to alert the docs team of big
changes coming in a release that will impact the install guide, etc.

From my point of view, I've historically pushed nova developers to be
documenting new features within the nova devref since it was "closer to
home" and could be tied to landing said feature in the nova tree, so
there was more oversight on the docs actually happening *somewhere*
rather than a promise to work them in the non-nova manuals, which a lot
of the time was lip service and didn't actually happen once the feature
was in. But there is still the need for the install guide as the first
step to deploying nova so we need to balance both things.

If no one else steps up for the docs liaison role, by default it lands
on me, so I'd appreciate any help here.

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

--

Thanks,

Matt Riedemann



__
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] [packaging] Openstack packaged on Gentoo

2017-02-27 Thread Nicolas Bock

On Mon, Feb 27, 2017 at 08:44:30AM -0600, Matthew Thode wrote:

After a short delay for reasons Openstack is now up to date on Gentoo.
Just `emerge =sys-cluster/openstack-meta-2017.1.` with your desired
use flags to pull in the head of the services stable branches and their
dependencies.


Thanks!


--
Matthew Thode (prometheanfire)



signature.asc
Description: PGP signature
__
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] dashboard login screen with domain drop-down

2016-09-15 Thread Nicolas Bock
Hi Brad,

thanks!

Nick

On Thu, Sep 15, 2016 at 3:50 PM, Brad Pokorny <brad_poko...@symantec.com> wrote:
> There's not a way to configure Horizon to do what you want, so you'd have
> to write custom code to do that.
>
> Also, there are security considerations to do it. Note that the default v3
> keystone policy[1] doesn't allow just any user to list all domains in the
> cloud. The list of domains is potentially information you wouldn't want an
> attacker to have, and if the list is on the Horizon login screen, anyone
> can see it.
>
> [1]
> https://github.com/openstack/keystone/blob/master/etc/policy.v3cloudsample.
> json#L32
>
> Brad
>
> On 9/15/16, 2:22 PM, "Nicolas Bock" <nicolasb...@gmail.com> wrote:
>
>>Hi,
>>
>>when I deploy the dashboard with
>>`OPENSTACK_KEYSTONE_MULTIDOMAIN_SUPPORT` turned on, the login screen
>>gains a new text field for the domain. Is it possible to turn that
>>text field into a multiple choice drop down menu?
>>
>>Thanks,
>>
>>Nick
>>
>>___
>>Mailing list:
>>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>Post to : openstack@lists.openstack.org
>>Unsubscribe :
>>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


[Openstack] dashboard login screen with domain drop-down

2016-09-15 Thread Nicolas Bock
Hi,

when I deploy the dashboard with
`OPENSTACK_KEYSTONE_MULTIDOMAIN_SUPPORT` turned on, the login screen
gains a new text field for the domain. Is it possible to turn that
text field into a multiple choice drop down menu?

Thanks,

Nick

___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack


Re: [Openstack] Liberty: (path|segment)_mtu values

2016-07-07 Thread Nicolas Bock
On 07/07/2016 09:26 PM, Matt Kassawara wrote:
> The effect of these options depends on your version of Liberty. Some
> patches fixing MTU implementation in Mitaka+ were backported to Liberty [1].
> 
> [1] https://review.openstack.org/#/c/305782/
> 
Thanks for the pointer Matt. I have started reading the source code,
which already made a few things much clearer.

Nick

> On Mon, Jul 4, 2016 at 2:18 AM, Nicolas Bock <nicolasb...@gmail.com
> <mailto:nicolasb...@gmail.com>> wrote:
> 
> Hi,
> 
> I am trying to understand the effect of the variables `path_mtu` and
> `segment_mtu` of `ml2_conf.ini`.
> 
> - Is it necessary to set values for those two variables?
> - What does neutron do with the values for those variables?
> - According to the documentation, a value of <= 0 means that the
> (path|segment)_mtu values are indeterminate. What does neutron do in
> this case?
> 
> Thanks,
> 
> Nick
> 
> 
> ___
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> <mailto:openstack@lists.openstack.org>
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> 
> 




signature.asc
Description: OpenPGP digital signature
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack