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