[openstack-dev] [chef] Retiring openstack/openstack-chef-repo

Samuel Cassiba s at cassiba.com
Sun Sep 2 17:41:18 UTC 2018


The entry point to Chef OpenStack, the openstack-chef-repo, is being
retired in favor of openstack/openstack-chef. As such, the watch ends
for openstack/openstack-chef-repo.

>From a Chef perspective, openstack-chef-repo has been a perfectly
adequate name, due to the prevalence of monorepos called 'chef-repo'.
In the Chef ecosystem, this makes perfect sense back in 2014 or 2015.
In more recent time, based on the outsider perspective from people who
were not nearly as immersed in the nomenclature, "why do you call it
repo?" had started to emerge as a FAQ.

Both repositories were created with the same intent: the junction of
OpenStack and Chef. However, openstack-chef existed before its time,
boxed and packed away to the attic long before Chef OpenStack was even
a notion.

With the introduction of documentation being published to docs.o.o, it
seemed like the logical time to migrate the entry point back to
openstack/openstack-chef. With assistance from infra doing the heavy
lifting for unretiring the project, openstack-chef was brought down
from the attic and de-mothballed.

At the time of this writing, no new changes are being merged to
openstack-chef-repo, and its jobs are noop. Focus has shifted entirely
to openstack/openstack-chef, with it being the entry point for Zuul
jobs, as well as Kitchen scenarios and documentation.

All stable jobs going back to stable/ocata have been migrated, with
the exception of the Cinder cookbook's Ocata release. It no longer
tests cleanly due to the detritus of time, so it will remain in its
current state.

The retirement festivities can be found at

If you have any questions or concerns, please don't hesitate to reach out.

Samuel Cassiba (scas)

More information about the OpenStack-dev mailing list