Forming the OpenDev Advisory Board
Hello everyone,
I've BCC'd potentially interested parties to ensure they get this email, but didn't CC to avoid putting too much pressure on them if I've gauged potential interest poorly. I'm also sure that this list isn't complete. Please share it with others that may be interested.
One of the governance bodies that we've described is the OpenDev Advisory Board [0]. The purpose of this group is to work with the OpenDev admins to ensure that project and resource provider needs are being met. Through this group OpenDev can communicate important updates, manage load on cloud resources over time, and plan for future needs. I'm also hopeful that it can serve as a conduit for our collaborating constituents to find time to help administer OpenDev as well.
We would like to welcome both projects consuming OpenDev resources and OpenDev resource providers to join the Advisory Board. The OpenDev admins don't want to prescribe how various groups decide who represents them as what works for OpenStack may not work for Zuul or Vexxhost. I don't expect this will be a large time sink, more that we'll have better communication channels when necessary. Once a participating group has decided who their representation should be, it would be great to have that representative reply to this thread publicly and introduce themselves. This way we'll build a roster over time.
For Advisory Board process, I'd like to avoid making it heavyweight and suggest using this mailing list (service-discuss@lists.opendev.org) with a subject tag of [AdvisoryBoard]. That said, I think the Advisory Board can decide if something else would work better for them once we've started to collect a roster here.
[0] https://docs.opendev.org/opendev/system-config/latest/project.html#governanc...
Clark
On Thu, May 21, 2020 at 2:41 PM Clark Boylan cboylan@sapwetik.org wrote:
Hello everyone,
I've BCC'd potentially interested parties to ensure they get this email, but didn't CC to avoid putting too much pressure on them if I've gauged potential interest poorly. I'm also sure that this list isn't complete. Please share it with others that may be interested.
One of the governance bodies that we've described is the OpenDev Advisory Board [0]. The purpose of this group is to work with the OpenDev admins to ensure that project and resource provider needs are being met. Through this group OpenDev can communicate important updates, manage load on cloud resources over time, and plan for future needs. I'm also hopeful that it can serve as a conduit for our collaborating constituents to find time to help administer OpenDev as well.
We would like to welcome both projects consuming OpenDev resources and OpenDev resource providers to join the Advisory Board. The OpenDev admins don't want to prescribe how various groups decide who represents them as what works for OpenStack may not work for Zuul or Vexxhost. I don't expect this will be a large time sink, more that we'll have better communication channels when necessary. Once a participating group has decided who their representation should be, it would be great to have that representative reply to this thread publicly and introduce themselves. This way we'll build a roster over time.
For Advisory Board process, I'd like to avoid making it heavyweight and suggest using this mailing list (service-discuss@lists.opendev.org) with a subject tag of [AdvisoryBoard]. That said, I think the Advisory Board can decide if something else would work better for them once we've started to collect a roster here.
[0] https://docs.opendev.org/opendev/system-config/latest/project.html#governanc...
Clark
I am very interested in participating in this advisory board. As one of the smaller(est) providers of opendev infrastructure, I would be elated to represent these smaller providers on this board.
W dniu 21.05.2020 o 20:40, Clark Boylan pisze:
One of the governance bodies that we've described is the OpenDev Advisory Board [0]. The purpose of this group is to work with the OpenDev admins to ensure that project and resource provider needs are being met. Through this group OpenDev can communicate important updates, manage load on cloud resources over time, and plan for future needs. I'm also hopeful that it can serve as a conduit for our collaborating constituents to find time to help administer OpenDev as well.
We would like to welcome both projects consuming OpenDev resources and OpenDev resource providers to join the Advisory Board. The OpenDev admins don't want to prescribe how various groups decide who represents them as what works for OpenStack may not work for Zuul or Vexxhost. I don't expect this will be a large time sink, more that we'll have better communication channels when necessary. Once a participating group has decided who their representation should be, it would be great to have that representative reply to this thread publicly and introduce themselves. This way we'll build a roster over time.
For Advisory Board process, I'd like to avoid making it heavyweight and suggest using this mailing list (service-discuss@lists.opendev.org) with a subject tag of [AdvisoryBoard]. That said, I think the Advisory Board can decide if something else would work better for them once we've started to collect a roster here.
Thanks for invitation. I am interested in participating in Advisory Board.
I work for Red Hat as one of AArch64 (64-bit Arm) developers. Currently assigned to Linaro project where I work on getting AArch64 the first class citizen in OpenStack world.
Core developer in OpenStack Kolla project, aarch64 CI jobs maintainer.
On Thu, May 21, 2020, at 11:40 AM, Clark Boylan wrote:
Hello everyone,
I've BCC'd potentially interested parties to ensure they get this email, but didn't CC to avoid putting too much pressure on them if I've gauged potential interest poorly. I'm also sure that this list isn't complete. Please share it with others that may be interested.
One of the governance bodies that we've described is the OpenDev Advisory Board [0]. The purpose of this group is to work with the OpenDev admins to ensure that project and resource provider needs are being met. Through this group OpenDev can communicate important updates, manage load on cloud resources over time, and plan for future needs. I'm also hopeful that it can serve as a conduit for our collaborating constituents to find time to help administer OpenDev as well.
We would like to welcome both projects consuming OpenDev resources and OpenDev resource providers to join the Advisory Board. The OpenDev admins don't want to prescribe how various groups decide who represents them as what works for OpenStack may not work for Zuul or Vexxhost. I don't expect this will be a large time sink, more that we'll have better communication channels when necessary. Once a participating group has decided who their representation should be, it would be great to have that representative reply to this thread publicly and introduce themselves. This way we'll build a roster over time.
For Advisory Board process, I'd like to avoid making it heavyweight and suggest using this mailing list (service-discuss@lists.opendev.org) with a subject tag of [AdvisoryBoard]. That said, I think the Advisory Board can decide if something else would work better for them once we've started to collect a roster here.
[0] https://docs.opendev.org/opendev/system-config/latest/project.html#governanc...
Going to give this a quick bump. We've got ~3.5 volunteers so far which is great. Rather than wait for a certain number of people I think we'll move forward with who we've got by say July 2, 2020 and others can always join at a later date. This will help ensure that we keep things moving forward. Since membership isn't required having a cut off date for those interested makes sense. Thank you to those of you who have volunteered and looking forward to seeing more of you.
I'll send out an email to all those I've seen volunteer on July 3, 2020 in order to start formalizing communication channels.
Clark
On 2020-06-22 14:06:27 -0700 (-0700), Clark Boylan wrote: [...]
Since membership isn't required having a cut off date for those interested makes sense.
[...]
But as you point out there's really no cut-off for more folks getting involved, this is just a point in time where we can declare that our Advisory Board exists and formally document it.
Hi Clark & al, and sorry for the delay!
I would like to volunteer for the new Board, as an Airship representative.
Thank you, Matt
-----Original Message----- From: Clark Boylan cboylan@sapwetik.org Sent: Monday, June 22, 2020 4:06 PM To: service-discuss@lists.opendev.org Subject: Re: Forming the OpenDev Advisory Board
On Thu, May 21, 2020, at 11:40 AM, Clark Boylan wrote:
Hello everyone,
I've BCC'd potentially interested parties to ensure they get this email, but didn't CC to avoid putting too much pressure on them if I've gauged potential interest poorly. I'm also sure that this list isn't complete. Please share it with others that may be interested.
One of the governance bodies that we've described is the OpenDev Advisory Board [0]. The purpose of this group is to work with the OpenDev admins to ensure that project and resource provider needs are being met. Through this group OpenDev can communicate important updates, manage load on cloud resources over time, and plan for future needs. I'm also hopeful that it can serve as a conduit for our collaborating constituents to find time to help administer OpenDev as well.
We would like to welcome both projects consuming OpenDev resources and OpenDev resource providers to join the Advisory Board. The OpenDev admins don't want to prescribe how various groups decide who represents them as what works for OpenStack may not work for Zuul or Vexxhost. I don't expect this will be a large time sink, more that we'll have better communication channels when necessary. Once a participating group has decided who their representation should be, it would be great to have that representative reply to this thread publicly and introduce themselves. This way we'll build a roster over time.
For Advisory Board process, I'd like to avoid making it heavyweight and suggest using this mailing list (service-discuss@lists.opendev.org) with a subject tag of [AdvisoryBoard]. That said, I think the Advisory Board can decide if something else would work better for them once we've started to collect a roster here.
[0] https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.opendev.org_ opendev_system-2Dconfig_latest_project.html-23governance&d=DwIBAg&c=LF YZ-o9_HUMeMTSQicvjIg&r=_C5hC_103uW491yNPPpNmA&m=8ofdPC1wcUrK1Co--XV4Rq Hlv5-KFAphFxbCsHbh2to&s=woyFx-sKYJILZydimJX_OG3ZH3FNw594d0Aq9WlKvqM&e=
Going to give this a quick bump. We've got ~3.5 volunteers so far which is great. Rather than wait for a certain number of people I think we'll move forward with who we've got by say July 2, 2020 and others can always join at a later date. This will help ensure that we keep things moving forward. Since membership isn't required having a cut off date for those interested makes sense. Thank you to those of you who have volunteered and looking forward to seeing more of you.
I'll send out an email to all those I've seen volunteer on July 3, 2020 in order to start formalizing communication channels.
Clark
I just noticed that I forgot to send a reply for TripleO.
I nominate myself.
On 23 Jun 2020, at 21:10, MCEUEN, MATT MM9745@att.com wrote:
Hi Clark & al, and sorry for the delay!
I would like to volunteer for the new Board, as an Airship representative.
Thank you, Matt
-----Original Message----- From: Clark Boylan cboylan@sapwetik.org Sent: Monday, June 22, 2020 4:06 PM To: service-discuss@lists.opendev.org Subject: Re: Forming the OpenDev Advisory Board
On Thu, May 21, 2020, at 11:40 AM, Clark Boylan wrote:
Hello everyone,
I've BCC'd potentially interested parties to ensure they get this email, but didn't CC to avoid putting too much pressure on them if I've gauged potential interest poorly. I'm also sure that this list isn't complete. Please share it with others that may be interested.
One of the governance bodies that we've described is the OpenDev Advisory Board [0]. The purpose of this group is to work with the OpenDev admins to ensure that project and resource provider needs are being met. Through this group OpenDev can communicate important updates, manage load on cloud resources over time, and plan for future needs. I'm also hopeful that it can serve as a conduit for our collaborating constituents to find time to help administer OpenDev as well.
We would like to welcome both projects consuming OpenDev resources and OpenDev resource providers to join the Advisory Board. The OpenDev admins don't want to prescribe how various groups decide who represents them as what works for OpenStack may not work for Zuul or Vexxhost. I don't expect this will be a large time sink, more that we'll have better communication channels when necessary. Once a participating group has decided who their representation should be, it would be great to have that representative reply to this thread publicly and introduce themselves. This way we'll build a roster over time.
For Advisory Board process, I'd like to avoid making it heavyweight and suggest using this mailing list (service-discuss@lists.opendev.org) with a subject tag of [AdvisoryBoard]. That said, I think the Advisory Board can decide if something else would work better for them once we've started to collect a roster here.
[0] https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.opendev.org_ opendev_system-2Dconfig_latest_project.html-23governance&d=DwIBAg&c=LF YZ-o9_HUMeMTSQicvjIg&r=_C5hC_103uW491yNPPpNmA&m=8ofdPC1wcUrK1Co--XV4Rq Hlv5-KFAphFxbCsHbh2to&s=woyFx-sKYJILZydimJX_OG3ZH3FNw594d0Aq9WlKvqM&e=
Going to give this a quick bump. We've got ~3.5 volunteers so far which is great. Rather than wait for a certain number of people I think we'll move forward with who we've got by say July 2, 2020 and others can always join at a later date. This will help ensure that we keep things moving forward. Since membership isn't required having a cut off date for those interested makes sense. Thank you to those of you who have volunteered and looking forward to seeing more of you.
I'll send out an email to all those I've seen volunteer on July 3, 2020 in order to start formalizing communication channels.
Clark
On Mon, Jun 22, 2020 at 4:06 PM Clark Boylan cboylan@sapwetik.org wrote:
On Thu, May 21, 2020, at 11:40 AM, Clark Boylan wrote:
Hello everyone,
I've BCC'd potentially interested parties to ensure they get this email, but didn't CC to avoid putting too much pressure on them if I've gauged potential interest poorly. I'm also sure that this list isn't complete. Please share it with others that may be interested.
One of the governance bodies that we've described is the OpenDev Advisory Board [0]. The purpose of this group is to work with the OpenDev admins to ensure that project and resource provider needs are being met. Through this group OpenDev can communicate important updates, manage load on cloud resources over time, and plan for future needs. I'm also hopeful that it can serve as a conduit for our collaborating constituents to find time to help administer OpenDev as well.
We would like to welcome both projects consuming OpenDev resources and OpenDev resource providers to join the Advisory Board. The OpenDev admins don't want to prescribe how various groups decide who represents them as what works for OpenStack may not work for Zuul or Vexxhost. I don't expect this will be a large time sink, more that we'll have better communication channels when necessary. Once a participating group has decided who their representation should be, it would be great to have that representative reply to this thread publicly and introduce themselves. This way we'll build a roster over time.
For Advisory Board process, I'd like to avoid making it heavyweight and suggest using this mailing list (service-discuss@lists.opendev.org) with a subject tag of [AdvisoryBoard]. That said, I think the Advisory Board can decide if something else would work better for them once we've started to collect a roster here.
[0]
https://docs.opendev.org/opendev/system-config/latest/project.html#governanc...
Going to give this a quick bump. We've got ~3.5 volunteers so far which is great. Rather than wait for a certain number of people I think we'll move forward with who we've got by say July 2, 2020 and others can always join at a later date. This will help ensure that we keep things moving forward. Since membership isn't required having a cut off date for those interested makes sense. Thank you to those of you who have volunteered and looking forward to seeing more of you.
I'll send out an email to all those I've seen volunteer on July 3, 2020 in order to start formalizing communication channels.
Clark
Clark,
Thanks for the invitation! I'm interested in participating on behalf of Limestone Networks, one of the organizations sponsoring resources for OpenDev jobs. I operate the cloud that Limestone sponsors, and am happy to address any needs or issues that arise.
A quick intro to the CI cloud we host. Limestone is a bare-metal hosting provider. The cloud hosting OpenDev nodepool instances at Limestone is also shared with our internal CI system, which also uses Zuul and Nodepool.
Our internal jobs primarily consist of operating system image build jobs which proceed to test a variety of bare-metal scenarios, such as various RAID configurations, etc., in nodepool instances using nested virt. As a result, we rely heavily on properly functioning nested virt in this cloud for our internal jobs, so I am always interested to hear feedback from OpenDev users regarding the reliability of nested virt on our test nodes.
Logan
participants (7)
-
Clark Boylan
-
Donny Davis
-
Jeremy Stanley
-
Logan V.
-
Marcin Juszkiewicz
-
MCEUEN, MATT
-
Sorin Sbarnea