-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi
I'd like to announce a new project in the LAVA family.
(README file follows) http://xkcd.com/927/
Seriously, lava has way to many tiny pieces. It all started when we renamed launch-control to lava-dashboard and created lava-server in the process. Now it's getting in the way.
So here we are, lava-core is the start of the merge. Subsequent projects will slowly merge into the core. Then one day we may just get a package that is called 'lava', that ships a program called 'lava' that does useful stuff. (End of readme file)
The project has been registered on Launchpad already. I plan on proposing merge requests that move parts of the non-client pieces there. Existing projects shall remain as backwards compatible code imports from lava-core.
Thanks ZK
Cool! really too many small pieces.
On 15 April 2012 02:14, Zygmunt Krynicki zygmunt.krynicki@canonical.comwrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi
I'd like to announce a new project in the LAVA family.
(README file follows) http://xkcd.com/927/
Seriously, lava has way to many tiny pieces. It all started when we renamed launch-control to lava-dashboard and created lava-server in the process. Now it's getting in the way.
So here we are, lava-core is the start of the merge. Subsequent projects will slowly merge into the core. Then one day we may just get a package that is called 'lava', that ships a program called 'lava' that does useful stuff. (End of readme file)
The project has been registered on Launchpad already. I plan on proposing merge requests that move parts of the non-client pieces there. Existing projects shall remain as backwards compatible code imports from lava-core.
Thanks ZK -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJPib6QAAoJEOvx/vtfL8ZXXgQP+QHhT/4beTTW7+yCFehDwe6i iDNZVPAhjrXxeh8TFisfdnPP+8z9khkcQTyXOgJnC3T4vbmWNBTjDQTpkSg/0lzS O8a0YBkcdQ5RPDr1NNiLG7PoAJDUts8yY2DXk2C1ykWmqOZBw7NcRVaX/gQ1Ym75 JODbrtcO1vT+E5rBNYiEgMEELStJZfMGbfGzFI+d4ONz702SJNVDHcY7FReKuTDc nvOZ8zfW03fHFNobAAR5F57lGBz6oLZjz/nblsCJjA9tf20LPsQTUxkv6EkkEyd1 0CTkjQt60kHQB/FYoxLofJ76CR12gGGNLauAf+fQPBa4CG5MvMsd7fdDbMVa3iZh MKzOv206SPTmB7GHRVTfTqoeFwsXNEc7CnFvEWA9GbCUboqBxuYnEw95m1137+/7 B3XHqsBmuJC1KJrwNIAFTl41oRuHchwEeZv72wBxoMU+4MKVpHFz6F0P3aR9da4s Uty9z+Nk8lUyQBGMOy6GMzqlPnNNYPM/v3f0CBZkA+D9mtdD/pFJGkhm/xmyE23S 5NskNi7CXZ+m+kyONAzL3JagLnB7PE+L8tHbap3IKbxkPbB5kzz/3eWqK6Evq+3t eQJZzuEq8gmIzyHVYjtnRvWXigv3m/vQrkcFC9Gs36tNXG0lEO07DbLpj3ZTlQ03 K+VSjvjsNhMvdhitIY7I =DKzA -----END PGP SIGNATURE-----
linaro-validation mailing list linaro-validation@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-validation
On Sat, 14 Apr 2012 20:14:44 +0200, Zygmunt Krynicki zygmunt.krynicki@canonical.com wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi
I'd like to announce a new project in the LAVA family.
(README file follows) http://xkcd.com/927/
Seriously, lava has way to many tiny pieces. It all started when we renamed launch-control to lava-dashboard and created lava-server in the process. Now it's getting in the way.
Hi. I approve of the intent, but am a bit confused as to the scope. What existing components do you see as ending up in lava-core?
I guess at least lava-server, lava-dashboard, lava-scheduler.
lava-dispatcher? Not so sure about that one.
I see a branch proposing lava-tool for inclusion -- but lava-tool is used by the client side tools, and so seems to me to be a candidate for keeping somewhere else...
Cheers, mwh
W dniu 17.04.2012 03:05, Michael Hudson-Doyle pisze:
On Sat, 14 Apr 2012 20:14:44 +0200, Zygmunt Krynicki zygmunt.krynicki@canonical.com wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi
I'd like to announce a new project in the LAVA family.
(README file follows) http://xkcd.com/927/
Seriously, lava has way to many tiny pieces. It all started when we renamed launch-control to lava-dashboard and created lava-server in the process. Now it's getting in the way.
Hi. I approve of the intent, but am a bit confused as to the scope. What existing components do you see as ending up in lava-core?
I guess at least lava-server, lava-dashboard, lava-scheduler.
lava-dispatcher? Not so sure about that one.
Actually I only see the need of two packages that we work on:
1) lava-core, it will have everything that we work on that is installed on "server" machines: lava-{dispatcher,server,dashboard,scheduler,android-test} are going to be a part of that. The aggregate code size is tiny and the value of splitting the packages is arguably small in comparison to the fuss that is needed to keep them up to date separately.
2) lava-device-agent, it will have everything that we need to put on a test device. It _will_ share code with lava-core but the exact method is not set in stone yet. I need some time to experiment and see. Ideally we could keep it on one repository and just release separately. I really want one tree that it easy to manage, test, release and upgrade.
I see a branch proposing lava-tool for inclusion -- but lava-tool is used by the client side tools, and so seems to me to be a candidate for keeping somewhere else...
The copy of lava-tool in lava-core will be independent. Before the transition is complete this will simplify the process.
Thanks ZK
On Tue, 17 Apr 2012 10:57:03 +0200, Zygmunt Krynicki zygmunt.krynicki@linaro.org wrote:
W dniu 17.04.2012 03:05, Michael Hudson-Doyle pisze:
On Sat, 14 Apr 2012 20:14:44 +0200, Zygmunt Krynicki zygmunt.krynicki@canonical.com wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi
I'd like to announce a new project in the LAVA family.
(README file follows) http://xkcd.com/927/
Seriously, lava has way to many tiny pieces. It all started when we renamed launch-control to lava-dashboard and created lava-server in the process. Now it's getting in the way.
Hi. I approve of the intent, but am a bit confused as to the scope. What existing components do you see as ending up in lava-core?
I guess at least lava-server, lava-dashboard, lava-scheduler.
lava-dispatcher? Not so sure about that one.
Actually I only see the need of two packages that we work on:
- lava-core, it will have everything that we work on that is installed
on "server" machines: lava-{dispatcher,server,dashboard,scheduler,android-test} are going to be a part of that. The aggregate code size is tiny and the value of splitting the packages is arguably small in comparison to the fuss that is needed to keep them up to date separately.
As I said on IRC, I'd be wary of overly tight coupling here -- we don't want to have to have rabbit running to be able to install or run just the dispatcher. That sort of thing isn't an inevitable consequence of putting everything in the same branch, but it makes it easier to fall into that trap.
- lava-device-agent, it will have everything that we need to put on a
test device.
Uh, what about client side things like lava-dashboard-tool?
It _will_ share code with lava-core but the exact method is not set in stone yet. I need some time to experiment and see.
Well OK, but I hope we can still get useful work done while you're experimenting. I guess I'm worried that I don't have an idea of the scope of your plans in this area or the timeframe you are thinking of. I'm wary of temporary hacks that turn out not to be temporary.
Ideally we could keep it on one repository and just release separately. I really want one tree that it easy to manage, test, release and upgrade.
One repository, multiple releases would make some kinds of development easier for sure, but OTOH would not make releasing or upgrading easier AFAICS.
I see a branch proposing lava-tool for inclusion -- but lava-tool is used by the client side tools, and so seems to me to be a candidate for keeping somewhere else...
The copy of lava-tool in lava-core will be independent. Before the transition is complete this will simplify the process.
The reason I asked about lava-tool is that lava-dashboard-tool etc depend on it, so where do you see lava-*-tool going? Into lava-core as well? If not, then I really don't think we want to have two copies of the lava-tool code floating around.
Cheers, mwh
First I agree with this intent. And I am a little concern on the compatibility of installation/upgrade with the old one. Do we have considered the method for installation and update when we use lava-core? There maybe someone already using our lava now, If we did not consideration before, this maybe cause some trouble for them.
Here are some consideration from me, but don't have solution for them now:( It's probably that we will install and upgrade with command apt-get again, but will that can install like lava-deployment-tool we used now? or can we update the instance that deployed with lava-deployment-tool now at that time? Or do we still use the lava-deployment-tool to do the instance installation and update?
Thanks, Yongqin Liu. On 15 April 2012 02:14, Zygmunt Krynicki zygmunt.krynicki@canonical.comwrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi
I'd like to announce a new project in the LAVA family.
(README file follows) http://xkcd.com/927/
Seriously, lava has way to many tiny pieces. It all started when we renamed launch-control to lava-dashboard and created lava-server in the process. Now it's getting in the way.
So here we are, lava-core is the start of the merge. Subsequent projects will slowly merge into the core. Then one day we may just get a package that is called 'lava', that ships a program called 'lava' that does useful stuff. (End of readme file)
The project has been registered on Launchpad already. I plan on proposing merge requests that move parts of the non-client pieces there. Existing projects shall remain as backwards compatible code imports from lava-core.
Thanks ZK -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJPib6QAAoJEOvx/vtfL8ZXXgQP+QHhT/4beTTW7+yCFehDwe6i iDNZVPAhjrXxeh8TFisfdnPP+8z9khkcQTyXOgJnC3T4vbmWNBTjDQTpkSg/0lzS O8a0YBkcdQ5RPDr1NNiLG7PoAJDUts8yY2DXk2C1ykWmqOZBw7NcRVaX/gQ1Ym75 JODbrtcO1vT+E5rBNYiEgMEELStJZfMGbfGzFI+d4ONz702SJNVDHcY7FReKuTDc nvOZ8zfW03fHFNobAAR5F57lGBz6oLZjz/nblsCJjA9tf20LPsQTUxkv6EkkEyd1 0CTkjQt60kHQB/FYoxLofJ76CR12gGGNLauAf+fQPBa4CG5MvMsd7fdDbMVa3iZh MKzOv206SPTmB7GHRVTfTqoeFwsXNEc7CnFvEWA9GbCUboqBxuYnEw95m1137+/7 B3XHqsBmuJC1KJrwNIAFTl41oRuHchwEeZv72wBxoMU+4MKVpHFz6F0P3aR9da4s Uty9z+Nk8lUyQBGMOy6GMzqlPnNNYPM/v3f0CBZkA+D9mtdD/pFJGkhm/xmyE23S 5NskNi7CXZ+m+kyONAzL3JagLnB7PE+L8tHbap3IKbxkPbB5kzz/3eWqK6Evq+3t eQJZzuEq8gmIzyHVYjtnRvWXigv3m/vQrkcFC9Gs36tNXG0lEO07DbLpj3ZTlQ03 K+VSjvjsNhMvdhitIY7I =DKzA -----END PGP SIGNATURE-----
linaro-validation mailing list linaro-validation@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-validation
W dniu 17.04.2012 04:29, YongQin Liu pisze:
First I agree with this intent. And I am a little concern on the compatibility of installation/upgrade with the old one. Do we have considered the method for installation and update when we use lava-core?
Upgrade will be smooth and transparent. This month the release will include lava-core. Several existing projects will be converted to empty transitional packages that simply depend on the new component without providing any code themselves.
There maybe someone already using our lava now, If we did not consideration before, this maybe cause some trouble for them.
I will do my best for everyone not to notice anything changed ;-)
Here are some consideration from me, but don't have solution for them now:( It's probably that we will install and upgrade with command apt-get again, but will that can install like lava-deployment-tool we used now? or can we update the instance that deployed with lava-deployment-tool now at that time?
Lava deployment tool will work as before. Apt-get is a separate topic.
Or do we still use the lava-deployment-tool to do the instance installation and update?
For the moment yes, lava-deployment-tool + pip is our primary method of installation.
Even if we provide apt-get based installation method it is still useful to have virtualenvs with multiple installations for testing and development. I'll post my apt plans later this week.
Thanks ZK
Hi,
I haven't heard about Lava Core effort for a while already. What is the current status? Any news on this front?
BR,
-Abner
On Sat, 2012-04-14 at 20:14 +0200, Zygmunt Krynicki wrote:
Hi
I'd like to announce a new project in the LAVA family.
(README file follows) http://xkcd.com/927/
Seriously, lava has way to many tiny pieces. It all started when we renamed launch-control to lava-dashboard and created lava-server in the process. Now it's getting in the way.
So here we are, lava-core is the start of the merge. Subsequent projects will slowly merge into the core. Then one day we may just get a package that is called 'lava', that ships a program called 'lava' that does useful stuff. (End of readme file)
The project has been registered on Launchpad already. I plan on proposing merge requests that move parts of the non-client pieces there. Existing projects shall remain as backwards compatible code imports from lava-core.
Thanks ZK _______________________________________________ linaro-validation mailing list linaro-validation@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-validation
linaro-validation@lists.linaro.org
-
Abner Silva -
Michael Hudson-Doyle -
Spring Zhang -
YongQin Liu -
Zygmunt Krynicki -
Zygmunt Krynicki