Re: bootstrap-vz switching to single branch strategy

2015-05-03 Thread Tiago Ilieve
Anders,

 bootstrap-vz now runs on a single master branch and the old github pages 
 documentation has been removed (use bootstrap-vz.readthedocs.org instead).

This also makes the documentation easier to maintain. With GitHub
Pages (which is a great service, btw), we had to write some HTML and
set a Ruby environment (Jekyll + GH Pages gems) so we could build it
on our workstations. Now we can do the same using only Python (Sphinx
+ SimpleHTTPServer, doing that automatically in a virtualenv when
using tox) and writing something that is pretty close to markdown.

 bootstrap-vz now supports 5 different providers, has 20 plugins and is 
 integration tested from start to finish on 2 of those providers.
 With over 1000 commits, almost 60 forks, 205 closed issues and 1500 lines of 
 documentation bootstrap-vz has become a stable platform for bootstrapping 
 Debian images and I hope it has made working with the cloud and other 
 virtualization platforms just a little easier for people, because it 
 certainly has for me.

I guess those numbers alone don't tell us one of the best parts
(something we have been talking off-list): bootstrap-vz is a carefully
designed tool that is not only getting more stable after every issue
we close, but it is also very friendly for newcomers that wants to
help hacking on its code or just need to alter something for their own
needs.

Regarding tests, as you said on #74[1], we are just starting. The
possibilities are nearly endless.

 You can read more about it in the changelog.

The changelog link was broken, as it was referring to the old
`development` branch. This is a working one[2].

 A big thank you goes to Tiago for all his help in maintaining this project 
 and to everybody who has contributed through either code or just lent their 
 expertise via email. Thanks!

We all have to thank you for the great effort you put (talking
numbers, you are the author of over 75% of the commits!) on
bootstrap-vz for the last couple years (and even a few more if we
consider its predecessor, build-debian-cloud). Thank you very much!

Ps.: it's kinda funny that this announcement came exactly two years
after the first commit[3] on the project. :-)

[1]: https://github.com/andsens/bootstrap-vz/issues/74#issuecomment-96296546
[2]: https://github.com/andsens/bootstrap-vz/blob/29e0cff/CHANGELOG.rst
[3]: https://github.com/andsens/bootstrap-vz/commit/4dbdb38

On 2 May 2015 at 17:44, Anders Ingemann and...@ingemann.de wrote:
 Hi everybody!

 Just a quick update.

 bootstrap-vz now runs on a single master branch and the old github pages
 documentation has been removed (use bootstrap-vz.readthedocs.org instead).

 Any pull requests should now of course be sent to the master branch.
 I may still create feature branches if some new feature may disrupt the
 stability of bootstrap-vz, but they will not be as long lived as the
 previous ones.

 Tiago and I have fixed a few more bugs (+ one feature from John Wendell), so
 that we are down to 3-4 bugs and 8 missing enhancements. You can read more
 about it in the changelog.

 bootstrap-vz now supports 5 different providers, has 20 plugins and is
 integration tested from start to finish on 2 of those providers.
 With over 1000 commits, almost 60 forks, 205 closed issues and 1500 lines of
 documentation bootstrap-vz has become a stable platform for bootstrapping
 Debian images and I hope it has made working with the cloud and other
 virtualization platforms just a little easier for people, because it
 certainly has for me.

 A big thank you goes to Tiago for all his help in maintaining this project
 and to everybody who has contributed through either code or just lent their
 expertise via email. Thanks!

 Anders



-- 
Tiago Myhro Ilieve
Blog: http://blog.myhro.info/
GitHub: https://github.com/myhro/
Montes Claros - MG, Brasil


--
To UNSUBSCRIBE, email to debian-cloud-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/caldtke_74srped+f_0dhuvi+go1oafw+3r4jjdq1x3n-w8j...@mail.gmail.com



Re: bootstrap-vz switching to single branch strategy

2015-05-03 Thread Vincent Bernat
 ❦  3 mai 2015 04:43 +0200, Eirik Schwenke debian-li...@s.hypertekst.net :

 I was wondering; are there any plans to make it more usable as a
 regular user? It seems it shouldn't be necessary to run it as root (at
 least not in all use-cases)?

Have a look at unshare which allows to become root without any
privilege. However, you need to set kernel.unprivileged_userns_clone to
1.
-- 
Make it clear before you make it faster.
- The Elements of Programming Style (Kernighan  Plauger)


signature.asc
Description: PGP signature


HVM images on official Debian account

2015-05-03 Thread Ognyan Kulev

Hi,

When someone searches official Debian account and goes to 
https://aws.amazon.com/marketplace/pp/B00AA27RK4/ , it shows the freshly 
released version 8 and this is great. But the offered images cannot be 
used for t2.* instances. Probably the image is not HVM.


Could you please use HVM images by default, so that people that don't go 
through https://wiki.debian.org/Cloud/AmazonEC2Image/Jessie to benefit?


All the best,
Ognyan



signature.asc
Description: OpenPGP digital signature


Re: HVM images on official Debian account

2015-05-03 Thread Ognyan Kulev

На  3.05.2015 в 17:07, James Bromberger написа:

HVM is the primary image type and has already been provided to the AWS
Marketplace team for listing (both PVM and HVM were passed to them
simultaneously in the product load data set). HVM should be the
default - PVM images are provided for legacy (customers with Reserved
Instance committments on PVM based instance types).  AWS Marketplace is
also now telling me they can mark root volumes as detatchable (so I have
asked them to do so).


Do I understand correctly that we are still waiting for approval of the 
HVM images by the AWS team?


Detachability would be nice :-)

Thank you,
Ognyan



signature.asc
Description: OpenPGP digital signature