Matthew Oliver 6bd32d5900 Remove openstack-101 from status and meetbot
In discussions at the last PTG[1] and in subsequent First Contact
SIG meetings[2] we've decided that the #openstack-101 channel
should be removed and rolled into the #openstack-dev channel.

Why? Good qustion:
 - No one is good at sitting in and watching the #openstack-101
   channel outside of OUI training periods.
 - It would be better for new contributors to ask questions in
   a channel that people with the answers already activly monitor.
 - 101 is an American-ism, that not everyone in the world would
   understand.

This means that during OUI trainings there will be more noise in
openstack-dev. However, trainings mostly happen the weekend
before a summit, so at a very quiet time. And would mean trainees
would already have practice and now where to come for questions.

There is another patch[3] which will remove openstack-101 from
the accessbot.

Finally, as per renaming instructions[4], once these patches
land, a redirect will need to be created, the topic updated and
current residents of the channel will need to be informed to
relocate.

[1] https://etherpad.openstack.org/p/FC_SIG_Rocky_PTG
[2] https://wiki.openstack.org/wiki/First_Contact_SIG#Meeting_Agenda
[3] https://review.openstack.org/559250
[4] https://docs.openstack.org/infra/system-config/irc.html#renaming-an-irc-channel

Change-Id: I24710f24e7e640aabbf22353c25c24d2a8af9287
2018-04-06 12:24:18 +10:00
2016-07-15 12:04:48 -07:00
2017-05-01 15:45:33 -04:00
2017-12-19 08:57:33 -08:00
2016-06-02 10:47:36 +03:00
2014-09-30 12:40:59 -07:00
2017-03-02 20:09:39 +01:00
2017-05-18 08:19:06 -07:00
2017-01-12 15:32:46 -05:00

Puppet Modules

These are a set of puppet manifests and modules that are currently being used to manage the OpenStack Project infrastructure.

The main entry point is in manifests/site.pp.

In general, most of the modules here are designed to be able to be run either in agent or apply mode.

These puppet modules require puppet 2.7 or greater. Additionally, the site.pp manifest assumes the existence of hiera.

See http://docs.openstack.org/infra/system-config for more information.

Documentation

The documentation presented at http://docs.openstack.org/infra/system-config comes from git://git.openstack.org/openstack-infra/system-config repo's docs/source. To build the documentation use

$ tox -evenv python setup.py build_sphinx

Description
System configuration for the OpenDev Collaboratory
Readme 156 MiB
Languages
Jinja 37%
Python 36.7%
Shell 13.6%
Dockerfile 3.9%
JavaScript 3%
Other 5.8%