Hi All -
I'm working with Zuul on their pending project confirmation on behalf of
the OpenStack Foundation. As you may or may not know, Zuul will need to
do a presentation in front of the OpenStack Foundation Board. I've
started an etherpad [1] with a rough outline, but ultimately this should
be a community driven effort. If you are able to fill in some blanks,
we welcome your contribution!
Cheers,
Jimmy
[1]
https://etherpad.openstack.org/p/Zuul_2019_OSF_Project_Confirmation_Process
Greetings,
I have a project, that requires compilation for different targets.
Same commands, but each one has to be done separately.
I have seen how OpenStack does it:
https://github.com/openstack-infra/openstack-zuul-jobs/blob/master/zuul.d/j…
so we define dozens of jobs separately even if they differ only by single
element.
My idea was to define job compilation, in which it is Ansible playbook that
determines which target it should choose, based on job name:
(compilation.yaml - playbook)
- name: Set hardware and technology
set_fact:
hardware: "{{ zuul.job.split('.')[1] }}"
technology: "{{ zuul.job.split('.')[2] }}"
Now in project definition I can have something like this:
- project:
verification:
jobs:
- compilation.x86_64.old:
parent: compilation
- compilation.i686.old:
parent: compilation
- compilation.i686.future:
parent: compilation
But Zuul says, that compiation.x86_64.old is not defined.
In other words: I want to define job inside project definition. This will
mean that adding new variant I can only modify only 2 lines.
Is there any reason why it is impossible?
Kind regards,
Tomasz
Hi,
Since the last email update, we merged the Multi-Ansible spec:
https://zuul-ci.org/docs/zuul/developer/specs/multiple-ansible-versions.html
Tristan worked on adding a job filter to the trigger event, as discussed
previously on this list. The webtrigger patch is now based on that.
Tristan also continued working on zuul-runner and a set of patches to
support nodes with python3 only.
I finally finished the changes related to buildset docker registries
(also mentioned previously on this list). In the end, the system looks
to be easy to use, but there are a few moving parts. My next task is to
document how to set such a system up.
******************************
There are a lot of outstanding changes, and I'd like to attempt to
prioritize and sequence them to help us work through them together:
1) The multi-ansible series
While this is newer than the others on the list, it does address
significant technical debt. It would be really good to get this
finished and released before Ansible 2.5 goes out of maintenance
(it's the oldest supported Ansible and only receives security fixes).
2) The zuul-runner series
This has been in development for a long time, and has a significant
impact on the executor. It will almost certainly conflict with the
multi-ansible series, so let's work on getting this merged after
that.
3) The web authentication spec
This has been in development for a while, and folks working on it
recently signaled it's ready for review. This shouldn't conflict
with anything ahead of it, so we can review it as time permits.
4) The web authentication series
Once the spec lands, we can review the implementation which has been
developing in parallel.
Of course, there's lots of other stuff out there we can review as well,
and anyone is free to review anything they want. :) However, I think
if we agree to prioritize these major efforts as I suggest, we will be
able to focus on them together and make the most efficient progress.
Help write the next update email by updating
https://etherpad.openstack.org/p/zuul-update-email
Thanks,
Jim
Greetings,
I have set up zuul v3 using docker-compose, so on my host I can see
following containers running:
CONTAINER ID IMAGE COMMAND
CREATED STATUS PORTS NAMES
b47be7107613 zuul/zuul-web "/usr/bin/dumb-init …" 12
hours ago Up 18 minutes 0.0.0.0:9000->9000/tcp
docker_web_1
5b4fcd2a2238 zuul/zuul-executor "/usr/bin/dumb-init …" 12
hours ago Up 18 minutes
docker_executor_1
4fe739ae6ace zuul/zuul-scheduler "/usr/bin/dumb-init …" 12
hours ago Up 7 minutes
docker_scheduler_1
1c88df15bd55 zuul/nodepool-launcher "/usr/bin/dumb-init …" 12
hours ago Up 18 minutes 0.0.0.0:8022->8022/tcp
docker_launcher_1
682c8f4ece17 zookeeper "/docker-entrypoint.…" 12
hours ago Up 18 minutes 2181/tcp, 2888/tcp, 3888/tcp
docker_zk_1
3bcfaf604728 docker_logs "httpd-foreground" 12
hours ago Up 18 minutes 0.0.0.0:8000->80/tcp
docker_logs_1
151eee2a9f4a mariadb "docker-entrypoint.s…" 12
hours ago Up 12 hours 3306/tcp
Everything in real time works perfectly, but the problem is that I cannot
see the builds history. My web service cannot get
http://zuul-master.internal.com:9000/api/tenant/igor/buildsets
nor any other /api call.
It receives 404, tenant not found.
I doesn't look like firewall issue, nor I see any errors in docker-compose
logs.
Any idea what did I set wrongly here?
Kind regards,
Tomasz
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>*