Excerpts from Nick Coghlan's message of 2015-01-19 11:20 +10:00:
> I'd like to suggest one refinement: we should also make it easy to
> *clone* access policies when creating new ones, whether for a system
> pool or for a custom policy. The difference between "clone policy from
> " and "inherit poli
On 01/06/2015 04:24 PM, Dan Callaghan wrote:
> I've just published the first draft of the design proposal for job page
> improvements, which we are targetting for Beaker 21.
>
> https://beaker-project.org/dev/proposals/job-page-improvements.html
>
> It's proposing some substantial changes to the
On 01/14/2015 10:38 AM, Dan Callaghan wrote:
> Excerpts from Matt Jia's message of 2015-01-14 09:06 +10:00:
>> If I understand properly, a system would be in multiple system pools.
>> So how do we decide which
>> system pool's access policies would be used in the system? I think it
>> may be work
On 01/19/2015 10:49 AM, Nick Coghlan wrote:
> On 01/07/2015 10:36 AM, Amit Saha wrote:
>> From: "Dan Callaghan"
>>> Could we upload a Docker image to the registry which has the base distro
>>> plus all Beaker dependencies installed? Then we can avoid the first step
>>> of build_base_image.sh. You
On 01/07/2015 10:36 AM, Amit Saha wrote:
> From: "Dan Callaghan"
>> Could we upload a Docker image to the registry which has the base distro
>> plus all Beaker dependencies installed? Then we can avoid the first step
>> of build_base_image.sh. You could call the images
>> beaker-development-fedora
