Re: [rdo-dev] Strategy on packaging external dependencies in RDO + include Ansible in RDO
by Alan Pevec
On Fri, Mar 30, 2018 at 4:31 AM, Sam Doran <sdoran(a)redhat.com> wrote:
>> Ansible RPMs are already there
>> http://releases.ansible.com/ansible/rpm/release/epel-7-x86_64/ but they
>> depend on EPEL for additional deps.
>
> Ansible RPMs have always been there. I don't believe they depend on anything
> in EPEL.
You are correct, I had some stale info or mixed it up with something else.
Here is yum install output on an empty CentOS7 machine:
Installing:
ansible noarch 2.4.3.0-1.el7.ans /ansible-2.4.3.0-1.el7.ans.noarch
Installing for dependencies:
PyYAML x86_64 3.10-11.el7 base
libyaml x86_64 0.1.4-11.el7_0 base
python-babel noarch 0.9.6-8.el7 base
python-cffi x86_64 1.6.0-5.el7 base
python-enum34 noarch 1.0.4-1.el7 base
python-idna noarch 2.4-1.el7 base
python-ipaddress noarch 1.0.16-2.el7 base
python-jinja2 noarch 2.7.2-2.el7 base
python-markupsafe x86_64 0.11-10.el7 base
python-paramiko noarch 2.1.1-4.el7 extras
python-ply noarch 3.4-11.el7 base
python-pycparser noarch 2.14-1.el7 base
python-setuptools noarch 0.9.8-7.el7 base
python2-cryptography x86_64 1.7.2-1.el7_4.1 updates
python2-pyasn1 noarch 0.1.9-7.el7 base
sshpass x86_64 1.06-2.el7 extras
> sshpass and paramiko come from Extras, python2-cryptography comes from
> updates.
My concern is that if those were included in Extras for Ansible, they
would be removed from Extras together with ansible.
> I'm not sure if any of that is helpful since you mentioned it would need to
> be built by the appropriate SIG anyway.
Yes, ideally we would be able to get ConfigMgmt SIG going, in the
meantime other SIGs are rebuilding on their own e.g. Virt SIG/oVirt
did 2.4.3 http://cbs.centos.org/koji/buildinfo?buildID=21591
As a quickfix, we could also temporarily push this to RDO deps repo,
until we have rest of the plan ready.
>> BTW ideal approach would be to insert OpenStack use-cases into Ansible
>> upstream CI and make it voting, this could become reality with cross-project
>> CI efforts lead by openstack-infra. With that, Ansible master would never
>> break us!
>
> I don't entirely follow this, but I think it sounds like what I proposed
> above: having OpenStack test the devel branch of Ansible so Ansible
> Engineering can get feedback quickly if things are broken prior to a
> release. I know some of the OpenStack infra folks, and the networking team
> within Ansible has been doing a lot of work with them with Zuul for
> distributed CI. Myself and Ricardo Cruz on the Ansible side are very
> interested in hooking up more testing of Ansible as it relates to OpenStack
> using Zuul run by OpenStack Infra. Ricki and I talked about this a bunch at
> the PTG but have been working on other things since we got back.
Yes, above was forward-looking CD world where, given infinite CI
resources, everything is tested pre-commit across collaborating
projects.
Definitely trunk RPMs from devel branch are the step in that
direction, progression scale is:
no testing, push the latest release, hope for the best -> CI with
latest release -> CI with devel branch -> CI pre-commit
Cheers,
Alan
6 years, 3 months
State of distgit jobs for rdoproject
by Paul Belanger
Greetings,
With the zuulv3 migration wrapping up, I wanted to start a thread about projects
that use the package-distgit-check-jobs template. These are projects like:
openstack/cloudkittyclient-distgit
I wanted to raise the idea of maybe pushing these projects directly upstream into
git.openstack.org. The main reason would be to leverage the upstream testing
infrastructure upstream, and maybe increase adoption of rpm with other
openstack teams. It is also one less this we as RDO have to manage on our own.
>From a governance POV these could be under an rdoproject team, tripleo or some
other.
To me the main question is around publishing of RPM and DLRN. Given secrets are
now part of zuulv3, is there any external services running that we'd need to
worry about? Could the publishing process be run from openstack-infra service?
- Paul
6 years, 3 months
Zuul migration complete
by Paul Belanger
All,
We have officially finished migrating jobs from Jenkins to Zuulv3. Thank you to
everybody that helped, while it took a bit of time, I believe the majority of
jobs worked right out of the box.
Changes to rdo-jobs and config are now open to everybody, please take some time
to get involved in the clean up of zuul-migrate script. For now, the tripleo-ci
team takes over to clean up the periodic jobs.
Over the next few days, we'll finish cleaning up nodepool resources and start
the process to delete old jenkins jobs from config project.
Thanks again, and look forward to the future.
- Paul
6 years, 3 months
zuulv3 migration update
by Paul Belanger
Greetings,
Wanted to give an update to the zuulv3 migration process. As it stands right
now, all projects specific to the rdoproject.org have been fully migrated from
jenkins to zuulv3. Hopefully this process was transparent to you, for the most
part we were able to fully test everything before flipping the switch on a
project. However we did have a few issues with jobs, but thanks to jpena,
amoralej and number80, to name a few, we managed to land fixes quickly.
At this point, we are still waiting to complete the migration of tripleo-ci
jobs, this include OVB and various 3rd party CI jobs. We've been blocked by a
nodepool migration of upstream-centos-7 nodes, but I'm told that will be
finished today. Meaning, we are aiming for Monday morning to flip the switch on
the rest of the tripleo-ci specific projects.
Due to this, we are still converting JJB changes into ansible playbooks using
the zuul-migrate command, so I please hold of on moving forward with changes to
the new rdo-jobs project. If everything goes well on Monday, we'll remove the
freeze on config / rdo-jobs for people to start contributing to again.
Thanks for your patience during these last 3 weeks, and hopefully we'll be
wrapped up Monday. If you have any questions or problems, please reply here or
#rdo on freenode.
- Paul
6 years, 4 months
Upcoming Meetups
by Rain Leander
The following are the meetups I'm aware of over the next two weeks where
OpenStack and/or RDO enthusiasts are likely to be present. If you know of
others, please let me know, and/or add them to http://rdoproject.org/events
If there's a meetup in your area, it'd be super keen if you attended, took a
few pictures and especially wrote up a summary of what was covered. And, as
always, if you give me enough notice, I can send swag along with you.
~Rain.
* Tuesday July 03 in Dublin, IE: Containers, Cloud Native, Kubernetes,
Internet of Things, 5G, and Cloud -
https://www.meetup.com/OpenStack-Ireland/events/251675405/
* Monday July 09 in Portland, OR, US: OpenStack Birthday Social & Move To
Open Infrastructure - https://www.meetup.com/openstack-pdx/events/252038450/
* Tuesday July 10 in Palo Alto, CA, US: Cloud Native Open Infra Tech Day
(w/ Istio keynote, Hands-on Labs and cupcakes!) -
https://www.meetup.com/openstack/events/251802241/
* Tuesday July 10 in Köln, DE: The easy way to Hybrid Kubernetes on AWS,
Azure, GCP, OpenStack and Bare-Metal -
https://www.meetup.com/Cologne-Cloud/events/250356865/
* Thursday July 12 in Stockholm, SE: OpenStack's 8th birthday! -
https://www.meetup.com/OpenStack-User-Group-Sweden/events/252160544/
* Thursday July 12 in Washington, DC, US: OpenStack's 8th Birthday
Celebration - https://www.meetup.com/OpenStackDC/events/252279760/
* Thursday July 12 in Boston, MA, US: Tungsten Fabric: Open Source
Multi-Cloud Networking at Scale -
https://www.meetup.com/Openstack-Boston/events/251651010/
* Friday July 13 in Moscow, RU: Конференция к дню рождения OpenStack -
https://www.meetup.com/OpenStack-Russia/events/251509448/
--
K Rain Leander
OpenStack Community Liaison
Open Source and Standards Team
https://www.rdoproject.org/
http://community.redhat.com
6 years, 4 months
