dev-tools as non-root

[Giulio Fidente]

hi there,

as per subject, I made some changes to dev-tools to make it work
successfully as non-root.

I tested these changes on CentOS6 and F17, my pull request:

https://github.com/aeolus-incubator/dev-tools/pull/7

it also includes some changes to README.md as it now provides a list of
packages to be installed system-wide before launching the script.

I thought launching as non-root was useful to both end users and devs
cause it helps with the testing, isolation from the other system
components, deploying of more versions in parallel and also provides
some abstraction from the hosting distro.

Feedback is very much appreciated.
-- 
Giulio Fidente

[cwolferh]

On 11/26/2012 10:35 AM, Giulio Fidente wrote:
>  hi there,
>
>  as per subject, I made some changes to dev-tools to make it work
>  successfully as non-root.
>
>  I tested these changes on CentOS6 and F17, my pull request:
>
>  https://github.com/aeolus-incubator/dev-tools/pull/7
>
>  it also includes some changes to README.md as it now provides a list of
>  packages to be installed system-wide before launching the script.
>
>  I thought launching as non-root was useful to both end users and devs
>  cause it helps with the testing, isolation from the other system
>  components, deploying of more versions in parallel and also provides
>  some abstraction from the hosting distro.
>
>  Feedback is very much appreciated. 
Please see my comment here:
https://github.com/aeolus-incubator/dev-tools/pull/7

Thanks,
--Crag

[Giulio Fidente]

On 11/26/2012 08:14 PM, Crag Wolfe wrote:
>  On 11/26/2012 10:35 AM, Giulio Fidente wrote:
> > Feedback is very much appreciated.
>  
>  Please see my comment here:
>  https://github.com/aeolus-incubator/dev-tools/pull/7 
hi Crag,

following you comment on github, most of the diffs were already in the
run_as_sudo branch

I've reworked my changes against the run_as_sudo branch ... but the
script in there still assumes one can run sudo.

I'd vote instead for *dropping the root requirement completely*.

Assuming we can _always_ use rbenv (and that it would probably raise our
chances of success), we can just put in the wiki a short list of
packages needed for rbenv to work (which are in the number of 5 or 6)
and cover all cases with a single script

Also, in the run_as_sudo branch I see an additional cleanup script which
we won't need when dropping the root requirement.

By now I've added some 'HAVESUDO' var on top of the script which, if set
to 1, runs the sudo when needed.

By default such a var is set to 0 as if one install the required basic
packages and provides a RBENV version, there is no need for root
credentials at all.

If these changes look fine to you, I'd be happy to update the README
accordingly.

p.s. not sure what is the right place to continue such a discussion,
github or aeolus-devel?
-- 
Giulio Fidente

[Justin Clift]

On 27/11/2012, at 12:36 AM, Giulio Fidente wrote:
<snip>
>  p.s. not sure what is the right place to continue such a discussion,
>  github or aeolus-devel? 
As a first thought, having the discussion here instead of in GitHub
would probably be better, because everyone can read the mailing list
archives easily (just one place to search).

To me, that sounds better than having to look through issue history
on GitHub (especially for issue history of several projects).

But... I don't have a good example of having to look through GitHub
issues for something yet.  So, it might not actually be super
important. ;)

+ Justin

--
Aeolus Cloud Evangelist
http://www.aeolusproject.org

[Justin Clift]

On 26/11/2012, at 7:35 PM, Giulio Fidente wrote:
>  hi there,
>  
>  as per subject, I made some changes to dev-tools to make it work
>  successfully as non-root.
>  
>  I tested these changes on CentOS6 and F17, my pull request:
>  
>  https://github.com/aeolus-incubator/dev-tools/pull/7
>  
>  it also includes some changes to README.md as it now provides a list of
>  packages to be installed system-wide before launching the script.
>  
>  I thought launching as non-root was useful to both end users and devs
>  cause it helps with the testing, isolation from the other system
>  components, deploying of more versions in parallel and also provides
>  some abstraction from the hosting distro.
>  
>  Feedback is very much appreciated. 
As additional food-for-thought on this, Daniel Berrange (extremely
capable coder on libvirt team) wrote this a week ago:

 
https://berrange.com/posts/2012/11/20/what-devstack-does-to-your-host-whe...

It's about experience from trying out the OpenStack dev setup
scripts on Fedora 17 (it uses sudo).

+ Justin


>  -- 
>  Giulio Fidente 
--
Aeolus Cloud Evangelist
http://www.aeolusproject.org

[Giulio Fidente]

On 11/27/2012 01:45 AM, Justin Clift wrote:
>  On 27/11/2012, at 12:36 AM, Giulio Fidente wrote:
>  <snip>
> > p.s. not sure what is the right place to continue such a discussion,
> > github or aeolus-devel?
>  
>  As a first thought, having the discussion here instead of in GitHub
>  would probably be better, because everyone can read the mailing list
>  archives easily (just one place to search). 
for people interested in this, the discussion has moved to github, the
patch submitted was accepted, further improved and we ended up with a
script intended to be launched by a non privileged user, which uses sudo
to install few dependecies and one can even disable such a behaviour and
install the deps for himself

still, there is an issue raised from Martin who tried to run the script
as root and is facing some errors (apparently due to a bug in puppet)

https://github.com/aeolus-incubator/dev-tools/issues/9
-- 
Giulio Fidente