Hello :)
On Wed, Feb 27, 2019 at 1:26 PM Chris Morgan <mihalis68(a)gmail.com> wrote:
> I think the issue is that forum submissions building on what gets
> discussed in Berlin can't be expected to be finalised whilst attendees to
> the berlin meetup are still traveling. It's not that Erik can't pull these
> things together, in fact he's an old hand at this, it's more that this
> process isn't reasonable if there's so little time to collate what we learn
> in Berlin and feed it forward to Denver. Frankly it sounds like because the
> planning committee needs 5 weeks, Erik can have two days. Seem unfair.
>
Honestly, the decision process doesn't take much time, aside from
organizing a time that all 10 people can meet across x timezones (a thing
unto itself). Its the community feedback period, giving people enough time
to secure travel approval from their management, loading the sessions into
the actual schedule app, and other print deadlines that force us to have
everything set this far out.
I will definitely help the ops community in whatever way I can! Do you have
remote attendance set up for the meetup?
> Chris
>
> On Wed, Feb 27, 2019 at 2:29 PM Kendall Nelson <kennelson11(a)gmail.com>
> wrote:
>
>> Another- nother thought: You could take a look at what is submitted by
>> project teams closer to the deadline and see if your ideas might fit well
>> with theirs since they are looking for feedback from operators anyway. In
>> the past I have always hoped for more engagement in the forum sessions I've
>> submitted but only ever had one or two operators able to join us.
>>
>> -Kendall (diablo_rojo)
>>
>> On Wed, Feb 27, 2019 at 11:14 AM Kendall Nelson <kennelson11(a)gmail.com>
>> wrote:
>>
>>> Hello :)
>>>
>>> On Wed, Feb 27, 2019 at 11:08 AM Jimmy McArthur <jimmy(a)openstack.org>
>>> wrote:
>>>
>>>> Erik,
>>>>
>>>> I definitely understand the timeline is tight. One of the reasons that
>>>> we publish the schedule so early is to enable community members to plan
>>>> their schedule early, especially as there is more overlap with the main
>>>> Summit Schedule in Denver. Additionally, travel approval is often
>>>> predicated upon someone showing they're leading/moderating a session.
>>>>
>>>> Before publishing the schedule, we print a draft Forum schedule for
>>>> community feedback and start promotion of the schedule, which we have to
>>>> put up on the OpenStack website and apps at 5 weeks out. Extending the date
>>>> beyond the 10th won't give the Forum Selection Committee enough time to
>>>> complete those tasks.
>>>>
>>>> I think if the Ops team can come up with some high level discussion
>>>> topics, we'll be happy to put some holds in the Forum schedule for
>>>> Ops-specific content. diablo_rojo has also offered to attend some of the
>>>> Ops sessions remotely as well, if that would help you all shape some things
>>>> into actual sessions.
>>>>
>>>
>>> I'm definitely happy to help as much as I can. If you'll have something
>>> set up that I can call into (zoom, webex, bluejeans, hangout, whatever), I
>>> definitely will. I could also read through etherpads you take notes in and
>>> help summarize things into forum proposals.
>>>
>>> Another thing to note is that whatever you/we submit, it doesn't have to
>>> be award winning :) Its totally possible to change session descriptions and
>>> edit who the speaker is later.
>>>
>>> Other random thought, I know Sean McGinnis has attended a lot of the
>>> Operators stuff in the past so maybe he could help narrow things down too?
>>> Not to sign him up for more work, but I know he's written a forum propsal
>>> or two in the past ;)
>>>
>>>
>>>>
>>>> I wish I could offer a further extension, but extending it another week
>>>> would push too far into the process.
>>>>
>>>> Cheers,
>>>> Jimmy
>>>>
>>>> Erik McCormick <emccormick(a)cirrusseven.com>
>>>> February 27, 2019 at 12:43 PM
>>>>
>>>> Jimmy,
>>>>
>>>> I won't even get home until the 10th much less have time to follow up
>>>> with anyone. The formation of those sessions often come from
>>>> discussions spawned at the meetup and expanded upon later with folks
>>>> who could not attend. Could we at least get until 3/17? I understand
>>>> your desire to finalize the schedule, but 6 weeks out should be more
>>>> than enough time, no?
>>>>
>>>> Thanks,
>>>> Erik
>>>>
>>>> Jimmy McArthur <jimmy(a)openstack.org>
>>>> February 27, 2019 at 12:04 PM
>>>>
>>>> Hi Erik,
>>>>
>>>> We are able to extend the deadline to 11:59PM Pacific, March 10th.
>>>> That should give the weekend to get any additional stragglers in and still
>>>> allow the Forum Programming Committee enough time to manage the rest of the
>>>> approval and publishing process in time for people's travel needs, etc...
>>>>
>>>> For the Ops Meetup specifically, I'd suggest going a bit broader with
>>>> the proposals and offering to fill in the blanks later. For example, if
>>>> something comes up and everyone agrees it should go to the Forum, just
>>>> submit before the end of the Ops session. Kendall or myself would be happy
>>>> to help you add details a bit later in the process, should clarification be
>>>> necessary. We typically have enough spots for the majority of proposed
>>>> Forum sessions. That's not a guarantee, but food for thought.
>>>>
>>>> Cheers,
>>>> Jimmy
>>>>
>>>>
>>>> _______________________________________________
>>>> Airship-discuss mailing list
>>>> Airship-discuss(a)lists.airshipit.org
>>>> http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss
>>>>
>>>> Erik McCormick <emccormick(a)cirrusseven.com>
>>>> February 27, 2019 at 11:31 AM
>>>> Would it be possible to push the deadline back a couple weeks? I expect
>>>> there to be a few session proposals that will come out of the Ops Meetup
>>>> which ends the day before the deadline. It would be helpful to have a
>>>> little time to organize and submit things afterwards.
>>>>
>>>> Thanks,
>>>> Erik
>>>>
>>>> Jimmy McArthur <jimmy(a)openstack.org>
>>>> February 27, 2019 at 10:40 AM
>>>> Hi Everyone -
>>>>
>>>> A quick reminder that we are accepting Forum [1] submissions for the
>>>> 2019 Open Infrastructure Summit in Denver [2]. Please submit your ideas
>>>> through the Summit CFP tool [3] through March 8th. Don't forget to put
>>>> your brainstorming etherpad up on the Denver Forum page [4].
>>>>
>>>> This is not a classic conference track with speakers and presentations.
>>>> OSF community members (participants in development teams, operators,
>>>> working groups, SIGs, and other interested individuals) discuss the topics
>>>> they want to cover and get alignment on and we welcome your participation.
>>>> The Forum is your opportunity to help shape the development of future
>>>> project releases. More information about the Forum [1].
>>>>
>>>> If you have questions or concerns, please reach out to
>>>> speakersupport(a)openstack.org.
>>>>
>>>> Cheers,
>>>> Jimmy
>>>>
>>>> [1] https://wiki.openstack.org/wiki/Forum
>>>> [2] https://www.openstack.org/summit/denver-2019/
>>>> [3] https://www.openstack.org/summit/denver-2019/call-for-presentations
>>>> [4] https://wiki.openstack.org/wiki/Forum/Denver2019
>>>> ___________________________________________
>>>>
>>>>
>>> Hopefully that helps!
>>>
>>> -Kendall (diablo_rojo)
>>>
>>
>
> --
> Chris Morgan <mihalis68(a)gmail.com>
>
- Kendall Nelson (diablo_rojo)
Erik,
I definitely understand the timeline is tight. One of the reasons that
we publish the schedule so early is to enable community members to plan
their schedule early, especially as there is more overlap with the main
Summit Schedule in Denver. Additionally, travel approval is often
predicated upon someone showing they're leading/moderating a session.
Before publishing the schedule, we print a draft Forum schedule for
community feedback and start promotion of the schedule, which we have to
put up on the OpenStack website and apps at 5 weeks out. Extending the
date beyond the 10th won't give the Forum Selection Committee enough
time to complete those tasks.
I think if the Ops team can come up with some high level discussion
topics, we'll be happy to put some holds in the Forum schedule for
Ops-specific content. diablo_rojo has also offered to attend some of
the Ops sessions remotely as well, if that would help you all shape some
things into actual sessions.
I wish I could offer a further extension, but extending it another week
would push too far into the process.
Cheers,
Jimmy
> Erik McCormick <mailto:emccormick@cirrusseven.com>
> February 27, 2019 at 12:43 PM
> Jimmy,
>
> I won't even get home until the 10th much less have time to follow up
> with anyone. The formation of those sessions often come from
> discussions spawned at the meetup and expanded upon later with folks
> who could not attend. Could we at least get until 3/17? I understand
> your desire to finalize the schedule, but 6 weeks out should be more
> than enough time, no?
>
> Thanks,
> Erik
> Jimmy McArthur <mailto:jimmy@openstack.org>
> February 27, 2019 at 12:04 PM
> Hi Erik,
>
> We are able to extend the deadline to 11:59PM Pacific, March 10th.
> That should give the weekend to get any additional stragglers in and
> still allow the Forum Programming Committee enough time to manage the
> rest of the approval and publishing process in time for people's
> travel needs, etc...
>
> For the Ops Meetup specifically, I'd suggest going a bit broader with
> the proposals and offering to fill in the blanks later. For example,
> if something comes up and everyone agrees it should go to the Forum,
> just submit before the end of the Ops session. Kendall or myself
> would be happy to help you add details a bit later in the process,
> should clarification be necessary. We typically have enough spots for
> the majority of proposed Forum sessions. That's not a guarantee, but
> food for thought.
>
> Cheers,
> Jimmy
>
>
> _______________________________________________
> Airship-discuss mailing list
> Airship-discuss(a)lists.airshipit.org
> http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss
> Erik McCormick <mailto:emccormick@cirrusseven.com>
> February 27, 2019 at 11:31 AM
> Would it be possible to push the deadline back a couple weeks? I
> expect there to be a few session proposals that will come out of the
> Ops Meetup which ends the day before the deadline. It would be helpful
> to have a little time to organize and submit things afterwards.
>
> Thanks,
> Erik
>
> Jimmy McArthur <mailto:jimmy@openstack.org>
> February 27, 2019 at 10:40 AM
> Hi Everyone -
>
> A quick reminder that we are accepting Forum [1] submissions for the
> 2019 Open Infrastructure Summit in Denver [2]. Please submit your
> ideas through the Summit CFP tool [3] through March 8th. Don't forget
> to put your brainstorming etherpad up on the Denver Forum page [4].
>
> This is not a classic conference track with speakers and
> presentations. OSF community members (participants in development
> teams, operators, working groups, SIGs, and other interested
> individuals) discuss the topics they want to cover and get alignment
> on and we welcome your participation. The Forum is your opportunity
> to help shape the development of future project releases. More
> information about the Forum [1].
>
> If you have questions or concerns, please reach out to
> speakersupport(a)openstack.org <mailto:speakersupport@openstack.org>.
>
> Cheers,
> Jimmy
>
> [1] https://wiki.openstack.org/wiki/Forum
> [2] https://www.openstack.org/summit/denver-2019/
> [3] https://www.openstack.org/summit/denver-2019/call-for-presentations
> [4] https://wiki.openstack.org/wiki/Forum/Denver2019
> ___________________________________________
>
Hi Erik,
We are able to extend the deadline to 11:59PM Pacific, March 10th. That
should give the weekend to get any additional stragglers in and still
allow the Forum Programming Committee enough time to manage the rest of
the approval and publishing process in time for people's travel needs,
etc...
For the Ops Meetup specifically, I'd suggest going a bit broader with
the proposals and offering to fill in the blanks later. For example, if
something comes up and everyone agrees it should go to the Forum, just
submit before the end of the Ops session. Kendall or myself would be
happy to help you add details a bit later in the process, should
clarification be necessary. We typically have enough spots for the
majority of proposed Forum sessions. That's not a guarantee, but food
for thought.
Cheers,
Jimmy
> Erik McCormick <mailto:emccormick@cirrusseven.com>
> February 27, 2019 at 11:31 AM
> Would it be possible to push the deadline back a couple weeks? I
> expect there to be a few session proposals that will come out of the
> Ops Meetup which ends the day before the deadline. It would be helpful
> to have a little time to organize and submit things afterwards.
>
> Thanks,
> Erik
>
> Jimmy McArthur <mailto:jimmy@openstack.org>
> February 27, 2019 at 10:40 AM
> Hi Everyone -
>
> A quick reminder that we are accepting Forum [1] submissions for the
> 2019 Open Infrastructure Summit in Denver [2]. Please submit your
> ideas through the Summit CFP tool [3] through March 8th. Don't forget
> to put your brainstorming etherpad up on the Denver Forum page [4].
>
> This is not a classic conference track with speakers and
> presentations. OSF community members (participants in development
> teams, operators, working groups, SIGs, and other interested
> individuals) discuss the topics they want to cover and get alignment
> on and we welcome your participation. The Forum is your opportunity
> to help shape the development of future project releases. More
> information about the Forum [1].
>
> If you have questions or concerns, please reach out to
> speakersupport(a)openstack.org <mailto:speakersupport@openstack.org>.
>
> Cheers,
> Jimmy
>
> [1] https://wiki.openstack.org/wiki/Forum
> [2] https://www.openstack.org/summit/denver-2019/
> [3] https://www.openstack.org/summit/denver-2019/call-for-presentations
> [4] https://wiki.openstack.org/wiki/Forum/Denver2019
> ___________________________________________
>
Hi Everyone -
A quick reminder that we are accepting Forum [1] submissions for the
2019 Open Infrastructure Summit in Denver [2]. Please submit your ideas
through the Summit CFP tool [3] through March 8th. Don't forget to put
your brainstorming etherpad up on the Denver Forum page [4].
This is not a classic conference track with speakers and presentations.
OSF community members (participants in development teams, operators,
working groups, SIGs, and other interested individuals) discuss the
topics they want to cover and get alignment on and we welcome your
participation. The Forum is your opportunity to help shape the
development of future project releases. More information about the Forum
[1].
If you have questions or concerns, please reach out to
speakersupport(a)openstack.org <mailto:speakersupport@openstack.org>.
Cheers,
Jimmy
[1] https://wiki.openstack.org/wiki/Forum
[2] https://www.openstack.org/summit/denver-2019/
[3] https://www.openstack.org/summit/denver-2019/call-for-presentations
[4] https://wiki.openstack.org/wiki/Forum/Denver2019
___________________________________________
Hello,
This is the pre-calling for presentations at the OpenInfra Day in Vietnam
this year. If you love to visit Hanoi <https://en.wikipedia.org/wiki/Hanoi>,
the capital of Vietnam, and share your passion for the Open Infrastructure
of any topic (container, CI, deployment, edge computing, etc.), please let
me know by replying to this email. Below is the tentative information of
the event:
- Date: 31 August 2019
- Location: Hanoi, Vietnam
We are working with the OpenStack Foundation to organize the Upstream
Institute at the day so this will be a great opportunity for potential
contributors to come and learn. There is also a couple of PTLs and projects
core members have shown their interest in visiting Hanoi for this event.
We will send out the official call-for-presentations after we've done with
the logistic vendors and It would be around the beginning of May or sooner.
If you have any questions, please do not hesitate to contact me.
See you in Hanoi :)
Bests,
On behalf of VietOpenInfra Group.
P/S: Have a look at our last OpenInfra Day: https://2018.vietopenstack.org/
--
*Trinh Nguyen*
*www.edlab.xyz <https://www.edlab.xyz>*
Hi,
Recently Zuul was modified to include the change message (i.e., commit
message in Gerrit, PR message in GitHub) as a Zuul variable:
https://review.openstack.org/631207
Ansible applies jinja templating to the inventory file (which we rely on
for variables in many jobs). If the change message incidentally
included jinja escapes, then Ansible may fail to run due to syntax
errors or undefined variables.
To correct this, we agreed that allowing templating of the change
message was not useful and should be disabled. An initial approach
using "{% raw %}" / "{% endraw %}" was deemed too fragile (a change
message with "{% endraw %}" in it would defeat the fix). So we have
merged this change which uses an Ansible-specific YAML tag, "!unsafe",
to mark the string as untrusted input which should not be templated:
https://review.openstack.org/633930
This appears to be an elegant and complete solution.
Yet before we release the next version of Zuul with this, I think we
should consider possible ramifications a bit more. I can think of two
things that including YAML tags in the inventory *might* cause problems
with, and I'd like input on whether folks think these could be actual
problems, or are, instead, easily overcome. And of course, if you think
of other potential problems.
First, the YAML tag may make it more difficult for users who perform
automatic processing of inventory files collected after the job runs. I
know of know examples of that myself, and it seems like it should be
safe for us to say that if you're going to parse an Ansible YAML
inventory file, you should be using a YAML parser that understands
Ansible YAML tags. But perhaps someone knows of why this would be an
undue hardship.
The second is really a special case of the first. As our build page in
the Zuul web UI continues to become more sophisticated, we might want to
have it parse the inventory file much as it is now currently parsing the
job-output.json file. I don't recall any discussions of this, but if we
think it's likely, we should probably make sure that any Javascript YAML
parser we might use could handle the tag.
If we think that these issues, or any others that folks may think of,
make it worth avoiding the !unsafe tag, we could solve the problem by
base64 encoding the change message. Ansible has convenient jinja
filters for base64 decoding, and in fact, Ansible modules such as slurp
provide data in base64-encoded form. It would be easy for a job which
needed to inspect the change message to do so by running it through the
b64decode filter first.
However, if we think these issues are not blockers, the !unsafe tag
presents the simplest and most human-readable approach.
-Jim
Hello Everyone!
We are now accepting Forum [1] submissions for the 2019 Open Infrastructure
Summit in Denver [2]. Please submit your ideas through the Summit CFP tool
[3] through March 8th. Don't forget to put your brainstorming etherpad up
on the Denver Forum page [4].
This is not a classic conference track with speakers and presentations. OSF
community members (participants in development teams, operators, working
groups, SIGs, and other interested individuals) discuss the topics they
want to cover and get alignment on and we welcome your participation. The
Forum is your opportunity to help shape the development of future project
releases. More information about the Forum [1].
The timeline for submissions is as follows:
Feb 22nd | Formal topic submission tool opens:
https://www.openstack.org/summit/denver-2019/call-for-presentations.
March 8th | Deadline for proposing Forum topics. Scheduling committee
meeting to make draft agenda.
March 22nd | Draft Forum schedule published. Crowd sourced session conflict
detection. Forum promotion begins.
March 29th | Scheduling committee final meeting
April 5th | Forum schedule final
April 29th-May 1st | Forum Time!
If you have questions or concerns, please reach out to
speakersupport(a)openstack.org.
Cheers,
Kendall Nelson (diablo_rojo)
[1] https://wiki.openstack.org/wiki/Forum
[2] https://www.openstack.org/summit/denver-2019/
[3] https://www.openstack.org/summit/denver-2019/call-for-presentations
[4] https://wiki.openstack.org/wiki/Forum/Denver2019
Hello,
The add-build-sshkey isn't great with static node because the key
added to the authorized_keys isn't removed if the remove-build-sshkey
doesn't run. This results in key being leaked in authorized_keys
without bound.
Thus I proposed to add an option to cleanup keys before adding a new
one: https://review.openstack.org/632620 .
However this isn't great for static node that can be used by more
than one job concurrently (multi-slot). Though, multi-slot already
needs special trick to isolate workspaces and it seems like many
other roles assume the node is dedicated to the job.
Multi-slot node usage could be improved by using a dedicated user for
each job, e.g. the operator would create zuul-%d user, and nodepool
would set unique username for each zknode.
In the meantime, can we please consider 632620 as this works well
for single user static node.
Regards,
-Tristan
Hey Zuul community,
The agenda is now live for the Open Infrastructure Summit and there are quite a few Zuul talks - congratulations to all of the speakers!
View the agenda for the Open Infrastructure Summit Denver <https://www.openstack.org/summit/denver-2019/summit-schedule#day=2019-04-29>.
Zuul sessions include:
Moving your testing infrastructure from Jenkins to Zuul
Unleashing the power of Fabric: Orchestrating new performance features for SR-IOV VNFs
Getting a Neural Network Up and Running with OpenLab
Best Practice to Run Zuul on Kubernetes
Profiling and Optimizing Container Image Builds
Digital Transformation in the Finance Industry
If you haven’t already registered for the Summit, you’ll want to do so now before prices increase on February 27! Register here <https://openinfrasummitandptgdenver.eventbrite.com/>.
I’ll continue to share more information about the Summit as the date approaches. Let me know if you have any questions.
Thanks,
Claire