Priorities for production

[Seth Vidal]

We're still in a testing-mode for coprs right now and I'd like to think 
about what our highest priorities are for production.

Right now things I care about/ I have been told I should care about - no 
particular order:

- copr-cli
- fixing up the cases where a backend builder will hang/become 
abandoned
- figure out how we manage sizing of the prodcution cloud instance(s)
- way for user to specify that they need a larger builder for their 
software
- deletable coprs
- private coprs


what else is on other folks' lists?

-sv

[Sam Kottler]

Can you elaborate on private coprs? Would those just be unlisted or do they
actually have ACL's?

On Mon, Jan 28, 2013 at 3:42 PM, Seth Vidal <skvidal(a)fedoraproject.org&gt;wrote:

>  We're still in a testing-mode for coprs right now and I'd
> like to think
>  about what our highest priorities are for production.
>
>  Right now things I care about/ I have been told I should care about - no
>  particular order:
>
>  - copr-cli
>  - fixing up the cases where a backend builder will hang/become abandoned
>  - figure out how we manage sizing of the prodcution cloud instance(s)
>  - way for user to specify that they need a larger builder for their
>  software
>  - deletable coprs
>  - private coprs
>
>
>  what else is on other folks' lists?
>
>  -sv
>
>
>  ______________________________**_________________
>  copr-devel mailing list
>  copr-devel(a)lists.fedorahosted.**org <copr-devel(a)lists.fedorahosted.org&gt;
>
> https://lists.fedorahosted.**org/mailman/listinfo/copr-**devel<https:/...
>

[Seth Vidal]

On Mon, 28 Jan 2013, Sam Kottler wrote:

>  Can you elaborate on private coprs? Would those just be unlisted or
> do they actually have ACL's?
>  
At the moment the idea is that they would have simple password protection. 
Not much else. That is still up in the air but they are a requested 
feature by Spot and some other folks whose opinions matter to me :)

I don't think it is likely they would become actually ACL based - but I if 
the code to handle it is forthcoming I suspect it would be entertained.

-sv

[Bohuslav Kabrda]

----- Original Message -----
>  
>  
>  On Mon, 28 Jan 2013, Sam Kottler wrote:
>  
>  > Can you elaborate on private coprs? Would those just be unlisted or
>  > do they actually have ACL's?
>  >
>  
>  At the moment the idea is that they would have simple password
>  protection.
>  Not much else. That is still up in the air but they are a requested
>  feature by Spot and some other folks whose opinions matter to me :)
>  
>  I don't think it is likely they would become actually ACL based - but
>  I if
>  the code to handle it is forthcoming I suspect it would be
>  entertained.
>  
>  -sv
>   
I guess this has two levels - private on frontend and private on backend.
On frontend we can do that easily with some additional protection, although it would
probably mean a need to solve [1]. I suppose some closed groups might want to cooperate on
building something, so we either give them all the same password or allow copr owners
adding (inviting?) other users as mentioned in [1] - and making these coprs only
accessible to these.
I'm wondering how to make coprs private at backend...?

-- 
Regards,
Bohuslav "Slavek" Kabrda.

[1] https://fedorahosted.org/copr/ticket/10

[Seth Vidal]

On Tue, 29 Jan 2013, Bohuslav Kabrda wrote:

>  ----- Original Message -----
> >
> >
> > On Mon, 28 Jan 2013, Sam Kottler wrote:
> >
> >> Can you elaborate on private coprs? Would those just be unlisted or
> >> do they actually have ACL's?
> >>
> >
> > At the moment the idea is that they would have simple password
> > protection.
> > Not much else. That is still up in the air but they are a requested
> > feature by Spot and some other folks whose opinions matter to me :)
> >
> > I don't think it is likely they would become actually ACL based - but
> > I if
> > the code to handle it is forthcoming I suspect it would be
> > entertained.
> >
> > -sv
> >
>
>  I guess this has two levels - private on frontend and private on backend.
>  On frontend we can do that easily with some additional protection, although it would
> probably mean a need to solve [1]. I suppose some closed groups might want to cooperate on
> building something, so we either give them all the same password or allow copr owners
> adding (inviting?) other users as mentioned in [1] - and making these coprs only
> accessible to these.
>  I'm wondering how to make coprs private at backend...? 
I've struggled with that, too. We'd need some sort of authenticator for 
the backend - but the trick is this - it has to be an authenticator a user 
can use with yum - otherwise getting to the repo for use will be pretty 
difficult.

-sv

[Seth Vidal]

On Tue, 29 Jan 2013, Seth Vidal wrote:

>  I've struggled with that, too. We'd need some sort of authenticator for the 
>  backend - but the trick is this - it has to be an authenticator a user can 
>  use with yum - otherwise getting to the repo for use will be pretty 
>  difficult.
>  

so here's my simple concept for how to password protect a copr:

1. we'll need to record a password in the frontend interface and in the db 
- ideally encrypt the password just like apache does with htpasswd

2. the backend will write out a .htpasswd and .htaccess that lets the 
builders get unimpeded access to the repo but anyone externally gets the 
password prompt

3. the username will be the same as the copr name.


Then the yum config can set a username and password and that SHOULD just 
work.


it's not complicated but it seems like it should cover our bases.

thoughts?
-sv