- Original Message -
> From: "Dan Callaghan"
> To: "beaker-devel"
> Sent: Tuesday, February 17, 2015 8:59:11 AM
> Subject: Re: [Beaker-devel] Building beaker from sources
>
> Excerpts from Jaroslav Kortus's message of 2015-02-16 21:30 +10:00:
> > On 02/16/2015 01:00 AM, Amit Saha wrote
- Original Message -
> From: "Nick Coghlan"
> To: beaker-devel@lists.fedorahosted.org
> Sent: Monday, February 16, 2015 6:30:53 PM
> Subject: Re: [Beaker-devel] Design proposal: Predefined Access Policies
> for Systems
>
> On 02/16/2015 06:09 PM, Amit Saha wrote:
> >> From: "Nick
> From: "Dan Callaghan"
> > Something this does suggest to me is that it should be possible to have
> > "open pools", where everyone with an account on the Beaker instance is
> > able to add their systems. In access policy rules, I believe "Everybody"
> > is indicated by having both the group and
Excerpts from Nick Coghlan's message of 2015-02-16 18:30 +10:00:
> On 02/16/2015 06:09 PM, Amit Saha wrote:
> > For the use case that a pool owner creates a pool, adds systems to
> > it and wants to use the same pool policy across systems - your
> > suggestion is perfect. What if I want to
> > ma
Excerpts from Jaroslav Kortus's message of 2015-02-16 21:30 +10:00:
> On 02/16/2015 01:00 AM, Amit Saha wrote:
> > You can just do yum-builddep beaker.spec to install the dependencies
> > and then
> > execute Misc/rpmbuild.sh -bs to just build the SRPM and Misc/rpmbuild.sh
> > -bb to
> > build th
On 02/16/2015 01:00 AM, Amit Saha wrote:
I found it quite difficult compared to my previous experience. Even the deps
listed in the
spec file are hard to download (wget downloads it as a different name from
what's expected
in the spec file).
You can just do yum-builddep beaker.spec to install
On 02/16/2015 06:01 PM, Amit Saha wrote:
>> Similarly "revoking a pool policy" doesn't make sense, the operation is
>> actually setting the system to use a custom policy. So this should also
>> be an option on bkr system-modify. Either --pool-policy='' which is
>> a bit awkward, or else a separate
On 02/16/2015 06:09 PM, Amit Saha wrote:
>> From: "Nick Coghlan"
>> of, rather than all pools. I think that's going to be easier to explain
>> in the documentation, rather than decoupling the two decisions and
>> having to explain that pool membership and pool policy inheritance are
>> actually un
- Original Message -
> From: "Nick Coghlan"
> To: beaker-devel@lists.fedorahosted.org
> Sent: Tuesday, February 10, 2015 12:33:47 PM
> Subject: Re: [Beaker-devel] Design proposal: Predefined Access Policies
> for Systems
>
> On 02/09/2015 10:37 AM, Amit Saha wrote:
> > So, here i
Excerpts from Alexander Todorov's message of 2015-01-12 19:55 +10:00:
> На 12.01.2015 в 06:43, Dan Callaghan написа:
> >
> > We could add a way for *users* to override the snippets in their recipe
> > XML. Maybe an element like
> >
> >
> > ...
> >
> >
> > But I don't know if that woul
- Original Message -
> From: "Dan Callaghan"
> To: "beaker-devel"
> Sent: Friday, February 13, 2015 3:28:05 PM
> Subject: Re: [Beaker-devel] Design proposal: Predefined Access Policies for
> Systems
>
> Excerpts from Amit Saha's message of 2015-02-06 12:12 +10:00:
> > We just publis
11 matches
Mail list logo
