You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Rohit Yadav <ro...@shapeblue.com> on 2016/04/19 13:22:51 UTC
[DISCUSS] ACS 4.9 systemvmtemplate
Hi all,
Will and I had some discussions around systemvm template on one of the PRs, I wanted to bring the discussion here on dev@.
Provided we've some features merged before the freeze date in May, we will need to build a new systemvm-template with likely following new packages (assuming the feature PRs get merged):
- Zebra and related packages required by OSPF stuff from Abhi
- Strongswan required by strongswan-vpn PR from Jayapal
To reduce scope, I suggest we still use Debian7 as base. As soon as these PRs get merged, we can create early systemvmtemplates in order to have them available for early testing (and against other PRs).
Will raised questions around where and how to build them -- I suppose we can reuse the systemvmtemplate builder Jenkins jobs (or create a new one if that's not working/broke) and we can use community-maintained hosting places to host them, I don't know if ASF can provide us any place to host them (S3, servers etc.). Comments, questions?
For long term (likely 4.10/LTS), I hope to have following work we can do around systemvm templates:
- Try to reduce systemvm template and systemvm.iso size
- Migrate to Debian 8 based base-template, newer packages and kernel
- Fix systemvm.iso init scripts (cloud early script, password-server script etc.) to be systemd compatible
- Evaluate and migrate Python scripts to using Python3 (if possible that would be great as more distros are moving to use Python 3.x as default)
- Migrate to using Java8 JRE (both for systemvm agents and mgmt. server)
- Migrate the systemvm build system to use packer with KVM, instead of using veewee/VirtualBox
Regards.
Regards,
Rohit Yadav
rohit.yadav@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
Re: [DISCUSS] ACS 4.9 systemvmtemplate
Posted by Will Stevens <ws...@cloudops.com>.
Thanks for starting this discussion Rohit. :)
*Will STEVENS*
Lead Developer
*CloudOps* *| *Cloud Solutions Experts
420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
w cloudops.com *|* tw @CloudOps_
On Tue, Apr 19, 2016 at 7:22 AM, Rohit Yadav <ro...@shapeblue.com>
wrote:
> Hi all,
>
> Will and I had some discussions around systemvm template on one of the
> PRs, I wanted to bring the discussion here on dev@.
>
> Provided we've some features merged before the freeze date in May, we will
> need to build a new systemvm-template with likely following new packages
> (assuming the feature PRs get merged):
>
> - Zebra and related packages required by OSPF stuff from Abhi
>
> - Strongswan required by strongswan-vpn PR from Jayapal
>
> To reduce scope, I suggest we still use Debian7 as base. As soon as these
> PRs get merged, we can create early systemvmtemplates in order to have them
> available for early testing (and against other PRs).
> Will raised questions around where and how to build them -- I suppose we
> can reuse the systemvmtemplate builder Jenkins jobs (or create a new one if
> that's not working/broke) and we can use community-maintained hosting
> places to host them, I don't know if ASF can provide us any place to host
> them (S3, servers etc.). Comments, questions?
>
> For long term (likely 4.10/LTS), I hope to have following work we can do
> around systemvm templates:
>
> - Try to reduce systemvm template and systemvm.iso size
>
> - Migrate to Debian 8 based base-template, newer packages and
> kernel
>
> - Fix systemvm.iso init scripts (cloud early script,
> password-server script etc.) to be systemd compatible
>
> - Evaluate and migrate Python scripts to using Python3 (if
> possible that would be great as more distros are moving to use Python 3.x
> as default)
>
> - Migrate to using Java8 JRE (both for systemvm agents and mgmt.
> server)
>
> - Migrate the systemvm build system to use packer with KVM,
> instead of using veewee/VirtualBox
>
> Regards.
>
> Regards,
>
> Rohit Yadav
>
> rohit.yadav@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> @shapeblue
>
Re: [DISCUSS] ACS 4.9 systemvmtemplate
Posted by Wido den Hollander <wi...@widodh.nl>.
> Op 19 april 2016 om 13:22 schreef Rohit Yadav <ro...@shapeblue.com>:
>
>
> Hi all,
>
> Will and I had some discussions around systemvm template on one of the PRs, I
> wanted to bring the discussion here on dev@.
>
> Provided we've some features merged before the freeze date in May, we will
> need to build a new systemvm-template with likely following new packages
> (assuming the feature PRs get merged):
>
> - Zebra and related packages required by OSPF stuff from Abhi
>
> - Strongswan required by strongswan-vpn PR from Jayapal
>
> To reduce scope, I suggest we still use Debian7 as base. As soon as these PRs
> get merged, we can create early systemvmtemplates in order to have them
> available for early testing (and against other PRs).
> Will raised questions around where and how to build them -- I suppose we can
> reuse the systemvmtemplate builder Jenkins jobs (or create a new one if that's
> not working/broke) and we can use community-maintained hosting places to host
> them, I don't know if ASF can provide us any place to host them (S3, servers
> etc.). Comments, questions?
>
> For long term (likely 4.10/LTS), I hope to have following work we can do
> around systemvm templates:
>
> - Try to reduce systemvm template and systemvm.iso size
>
> - Migrate to Debian 8 based base-template, newer packages and kernel
>
> - Fix systemvm.iso init scripts (cloud early script, password-server
> script etc.) to be systemd compatible
>
> - Evaluate and migrate Python scripts to using Python3 (if possible
> that would be great as more distros are moving to use Python 3.x as default)
>
> - Migrate to using Java8 JRE (both for systemvm agents and mgmt.
> server)
>
Yes, good move.
> - Migrate the systemvm build system to use packer with KVM, instead
> of using veewee/VirtualBox
>
Another good move!
Seems like that would be a good move overall.
Wido
> Regards.
>
> Regards,
>
> Rohit Yadav
>
> rohit.yadav@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> @shapeblue
Re: [DISCUSS] ACS 4.9 systemvmtemplate
Posted by Rohit Yadav <ro...@shapeblue.com>.
Thank for sharing Erik.
Regards.
________________________________________
From: Erik Weber <te...@gmail.com>
Sent: 19 April 2016 23:15
To: dev@cloudstack.apache.org
Subject: Re: [DISCUSS] ACS 4.9 systemvmtemplate
Regarding packer, I believe cosmic has done most of that. See
https://github.com/MissionCriticalCloud/systemvm-packer/blob/master/README.md
Erik
Den tirsdag 19. april 2016 skrev Rohit Yadav <ro...@shapeblue.com>
følgende:
> Hi all,
>
> Will and I had some discussions around systemvm template on one of the
> PRs, I wanted to bring the discussion here on dev@.
>
> Provided we've some features merged before the freeze date in May, we will
> need to build a new systemvm-template with likely following new packages
> (assuming the feature PRs get merged):
>
> - Zebra and related packages required by OSPF stuff from Abhi
>
> - Strongswan required by strongswan-vpn PR from Jayapal
>
> To reduce scope, I suggest we still use Debian7 as base. As soon as these
> PRs get merged, we can create early systemvmtemplates in order to have them
> available for early testing (and against other PRs).
> Will raised questions around where and how to build them -- I suppose we
> can reuse the systemvmtemplate builder Jenkins jobs (or create a new one if
> that's not working/broke) and we can use community-maintained hosting
> places to host them, I don't know if ASF can provide us any place to host
> them (S3, servers etc.). Comments, questions?
>
> For long term (likely 4.10/LTS), I hope to have following work we can do
> around systemvm templates:
>
> - Try to reduce systemvm template and systemvm.iso size
>
> - Migrate to Debian 8 based base-template, newer packages and
> kernel
>
> - Fix systemvm.iso init scripts (cloud early script,
> password-server script etc.) to be systemd compatible
>
> - Evaluate and migrate Python scripts to using Python3 (if
> possible that would be great as more distros are moving to use Python 3.x
> as default)
>
> - Migrate to using Java8 JRE (both for systemvm agents and mgmt.
> server)
>
> - Migrate the systemvm build system to use packer with KVM,
> instead of using veewee/VirtualBox
>
> Regards.
>
> Regards,
>
> Rohit Yadav
>
> rohit.yadav@shapeblue.com <javascript:;>
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> @shapeblue
>
Regards,
Rohit Yadav
rohit.yadav@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
Re: [DISCUSS] ACS 4.9 systemvmtemplate
Posted by Erik Weber <te...@gmail.com>.
Regarding packer, I believe cosmic has done most of that. See
https://github.com/MissionCriticalCloud/systemvm-packer/blob/master/README.md
Erik
Den tirsdag 19. april 2016 skrev Rohit Yadav <ro...@shapeblue.com>
følgende:
> Hi all,
>
> Will and I had some discussions around systemvm template on one of the
> PRs, I wanted to bring the discussion here on dev@.
>
> Provided we've some features merged before the freeze date in May, we will
> need to build a new systemvm-template with likely following new packages
> (assuming the feature PRs get merged):
>
> - Zebra and related packages required by OSPF stuff from Abhi
>
> - Strongswan required by strongswan-vpn PR from Jayapal
>
> To reduce scope, I suggest we still use Debian7 as base. As soon as these
> PRs get merged, we can create early systemvmtemplates in order to have them
> available for early testing (and against other PRs).
> Will raised questions around where and how to build them -- I suppose we
> can reuse the systemvmtemplate builder Jenkins jobs (or create a new one if
> that's not working/broke) and we can use community-maintained hosting
> places to host them, I don't know if ASF can provide us any place to host
> them (S3, servers etc.). Comments, questions?
>
> For long term (likely 4.10/LTS), I hope to have following work we can do
> around systemvm templates:
>
> - Try to reduce systemvm template and systemvm.iso size
>
> - Migrate to Debian 8 based base-template, newer packages and
> kernel
>
> - Fix systemvm.iso init scripts (cloud early script,
> password-server script etc.) to be systemd compatible
>
> - Evaluate and migrate Python scripts to using Python3 (if
> possible that would be great as more distros are moving to use Python 3.x
> as default)
>
> - Migrate to using Java8 JRE (both for systemvm agents and mgmt.
> server)
>
> - Migrate the systemvm build system to use packer with KVM,
> instead of using veewee/VirtualBox
>
> Regards.
>
> Regards,
>
> Rohit Yadav
>
> rohit.yadav@shapeblue.com <javascript:;>
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> @shapeblue
>