layout | permalink | title | tags | image | ||||
---|---|---|---|---|---|---|---|---|
page |
/campaigns/ |
Operations Campaigns |
|
|
Operations Campaigns are medium-term projects which are conducted as needed, when there is a request from EGI, an ROC site or a user community, which requires coordinated action at most or all sites. Campaigns should have a leader, who is responsible for getting sites to stick to a schedule or taking action; campaigns are also time-limited, meaning that they have to have a start and an end. They differ from projects in their
- Scope: Campaigns are usually of very limited scope, addressing a single focussed aspect of site services
- Impact on sites: Campaigns should affect all sites, hence the need for coordinated action
- Interested parties: Campaigns affect only the operations team
While this is just another way of doing what we've always been doing, it gives some more visibility to important ROC-wide tasks and allows clearer delegation of tasks. Also, it will allow us to report better to supporting projects such as well as relying parties like EGI.eu. Campaigns are documented on the Github wiki pages of the AAROC DevOps repo.
{% assign sortedcampaigns = site.data.campaigns | sort:"priority" | reverse %}
{% for campaign in sortedcampaigns %} {% if campaign.wiki != null %} {% else if campaign.page != null %} {% else %} {% endif %} {% endfor %}Name | Leader | State | Period | ||
---|---|---|---|---|---|
{{ campaign.name }} | {{ campaign.name }} | {{ campaign.name }} | {{ campaign.leader }} | {{ campaign.state.name }} | {{ campaign.start }} - {{ campaign.end }} |