nice explanation Will, c&p to the wiki and docs, i'd say
On Fri, Feb 17, 2017 at 6:06 PM, Will Stevens wrote:
> Yes. Exactly. The "patches" don't require a new system vm template to be
> distributed, but changes to the "appliance" does require a new system vm
> template.
>
> On Feb 17, 2017 12:04
Yes. Exactly. The "patches" don't require a new system vm template to be
distributed, but changes to the "appliance" does require a new system vm
template.
On Feb 17, 2017 12:04 PM, "David Mabry" wrote:
> Awesome. Thanks for the quick answer. That totally makes sense. Package
> changes (insta
Awesome. Thanks for the quick answer. That totally makes sense. Package
changes (installation, etc…) are done in the “appliance” section of code. Any
“config” changes required beyond package installation are done in the “patches”
section of code.
Thanks,
David Mabry
On 2/17/17, 10:52 AM, "
So the System VM is "built" from two sources.
1)
https://github.com/apache/cloudstack/tree/master/tools/appliance/definitions/systemvmtemplate
This defines what is actually built and is distributed as the SystemVM
Template. You MUST use it if you change the packages included in the
SystemVM templ
Hello everyone,
I’m looking at making some changes to the system vm, but I have found that
there looks like there are 2 different places in the code that “build” the
systemvm. There is there is
https://github.com/apache/cloudstack/tree/13bfdd71e6f52d2f613a802b3d16c9b40af7/systemvm/patches/
