You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Maurice Lawler <ma...@me.com> on 2013/10/03 01:00:01 UTC
System VM
Hello,
Going through the install, I noticed the system VM template hasnt
changed URL. Is it safe to assume to utilize this one:
# /usr/lib64/cloud/common/scripts/storage/secondary/cloud-install-sys-tmplt -m /mnt/secondary -u http://download.cloud.com/templates/acton/acton-systemvm-02062012.qcow2.bz2 -h kvm -s <optional-management-server-secret-key> -F
Or should I be utilizing another?
- Maurice
Re: System VM
Posted by Travis Graham <tg...@tgraham.us>.
From the perspective of a new community member being able to contribute to a separate repo that doesn't touch the app code is nice because that would open up the possibility of being a committer for the doc repo and separate that silo of work. Also less volatile in the fact that people, like me, who don't want to or can't mess with the actual Java side of the house and potentially having to deal with funky rebase issues and keeping up to date in the fast moving target state that the main code stays in.
There's talk of splitting the Release Manager out into separate roles with one head RM and sub RM's within their area of responsibility. I think this would help on that front as well. Having a lead Docs person (I think that's David?) who can oversee the whole process but can delegate things out to community members who are willing to take on the work.
That's my initial thoughts, I'm sure I could think of more advantages later once I work through more of the docs process. It's been interesting so far.
Travis
On Oct 4, 2013, at 1:55 PM, Chip Childers <ch...@sungard.com> wrote:
> On Fri, Oct 04, 2013 at 05:43:16PM +0000, Jessica Tomechak wrote:
>> Hi guys,
>> Not arguing against it, but I would be very much interested in your reasoning behind why having docs in a separate repo makes them easier to work on. What have we experienced since this time last year which has led us to reverse the original decision to keep docs in the same repo with code?
>>
>> And having mentioned this, also thanks to y'all for taking care of doing the actual split and setting up the new repo.
>>
>> Jessica T.
>
> Documentation has a different lifecycle from the code, since docs aren't
> usually complete anywhere near feature complete.
>
> Also, having it in a different repo will help contributors more easily
> work with the documentation. We are seeing a number of new folks in the
> community that want to help on that front.
>
> -chip
Re: System VM
Posted by sebgoa <ru...@gmail.com>.
On Oct 5, 2013, at 5:53 AM, Radhika Puthiyetath <ra...@citrix.com> wrote:
> Hi All,
>
> Before setting up the cloudstack repo, we argued that doc should be in a different repo. At that time, nobody listened to our argument of doc having a different life cycle.
>
Then we should have listened
> I am wondering why this back and forth decisions changes now for docs.
Things change Radhika: community gets bigger, code gets more complex, you have more releases under your belt, you learn from experience. You have cloudmonkey and you realize it needs to be separate, then you think about docs and you realize they might be better off in their own repo, you poll the community, reach consensus and you make the move.
Nothing else to read into it than trying to find mechanisms to have great docs and help people contribute to it.
-sebastien
>
> -----Original Message-----
> From: Chip Childers [mailto:chip.childers@sungard.com]
> Sent: Friday, October 04, 2013 11:25 PM
> To: dev@cloudstack.apache.org
> Subject: Re: System VM
>
> On Fri, Oct 04, 2013 at 05:43:16PM +0000, Jessica Tomechak wrote:
>> Hi guys,
>> Not arguing against it, but I would be very much interested in your reasoning behind why having docs in a separate repo makes them easier to work on. What have we experienced since this time last year which has led us to reverse the original decision to keep docs in the same repo with code?
>>
>> And having mentioned this, also thanks to y'all for taking care of doing the actual split and setting up the new repo.
>>
>> Jessica T.
>
> Documentation has a different lifecycle from the code, since docs aren't usually complete anywhere near feature complete.
>
> Also, having it in a different repo will help contributors more easily work with the documentation. We are seeing a number of new folks in the community that want to help on that front.
>
> -chip
RE: System VM
Posted by Radhika Puthiyetath <ra...@citrix.com>.
Hi All,
Before setting up the cloudstack repo, we argued that doc should be in a different repo. At that time, nobody listened to our argument of doc having a different life cycle.
I am wondering why this back and forth decisions changes now for docs.
-----Original Message-----
From: Chip Childers [mailto:chip.childers@sungard.com]
Sent: Friday, October 04, 2013 11:25 PM
To: dev@cloudstack.apache.org
Subject: Re: System VM
On Fri, Oct 04, 2013 at 05:43:16PM +0000, Jessica Tomechak wrote:
> Hi guys,
> Not arguing against it, but I would be very much interested in your reasoning behind why having docs in a separate repo makes them easier to work on. What have we experienced since this time last year which has led us to reverse the original decision to keep docs in the same repo with code?
>
> And having mentioned this, also thanks to y'all for taking care of doing the actual split and setting up the new repo.
>
> Jessica T.
Documentation has a different lifecycle from the code, since docs aren't usually complete anywhere near feature complete.
Also, having it in a different repo will help contributors more easily work with the documentation. We are seeing a number of new folks in the community that want to help on that front.
-chip
Re: System VM
Posted by Chip Childers <ch...@sungard.com>.
On Fri, Oct 04, 2013 at 05:43:16PM +0000, Jessica Tomechak wrote:
> Hi guys,
> Not arguing against it, but I would be very much interested in your reasoning behind why having docs in a separate repo makes them easier to work on. What have we experienced since this time last year which has led us to reverse the original decision to keep docs in the same repo with code?
>
> And having mentioned this, also thanks to y'all for taking care of doing the actual split and setting up the new repo.
>
> Jessica T.
Documentation has a different lifecycle from the code, since docs aren't
usually complete anywhere near feature complete.
Also, having it in a different repo will help contributors more easily
work with the documentation. We are seeing a number of new folks in the
community that want to help on that front.
-chip
RE: System VM
Posted by Jessica Tomechak <Je...@citrix.com>.
Hi guys,
Not arguing against it, but I would be very much interested in your reasoning behind why having docs in a separate repo makes them easier to work on. What have we experienced since this time last year which has led us to reverse the original decision to keep docs in the same repo with code?
And having mentioned this, also thanks to y'all for taking care of doing the actual split and setting up the new repo.
Jessica T.
________________________________________
From: David Nalley [david@gnsa.us]
Sent: Wednesday, October 02, 2013 4:38 PM
To: dev@cloudstack.apache.org
Subject: Re: System VM
On Wed, Oct 2, 2013 at 7:34 PM, Travis Graham <tg...@tgraham.us> wrote:
> Hey Marcus,
>
> The docs were split out today to make them easier to work on. I'll be going
> through them later tonight to fix things like this and sending out a diff
> to get them corrected as soon as possible.
>
> Travis
Hi Travis:
Lets try and make the patches small - perhaps one per file, or one per
several files, but not omnibus. It will be much easier to parse, and
apply, especially if something doesn't build cleanly.
--David
Re: System VM
Posted by David Nalley <da...@gnsa.us>.
On Wed, Oct 2, 2013 at 7:34 PM, Travis Graham <tg...@tgraham.us> wrote:
> Hey Marcus,
>
> The docs were split out today to make them easier to work on. I'll be going
> through them later tonight to fix things like this and sending out a diff
> to get them corrected as soon as possible.
>
> Travis
Hi Travis:
Lets try and make the patches small - perhaps one per file, or one per
several files, but not omnibus. It will be much easier to parse, and
apply, especially if something doesn't build cleanly.
--David
Re: System VM
Posted by Travis Graham <tg...@tgraham.us>.
Hey Marcus,
The docs were split out today to make them easier to work on. I'll be going
through them later tonight to fix things like this and sending out a diff
to get them corrected as soon as possible.
Travis
On Wednesday, October 2, 2013, Marcus Sorensen wrote:
> For 4.2 that doesn't work. If the docs say that, we need to fix it.
>
> On Wed, Oct 2, 2013 at 5:00 PM, Maurice Lawler <maurice.lawler@me.com<javascript:;>>
> wrote:
> > Hello,
> >
> > Going through the install, I noticed the system VM template hasnt changed
> > URL. Is it safe to assume to utilize this one:
> >
> > #
> /usr/lib64/cloud/common/scripts/storage/secondary/cloud-install-sys-tmplt
> > -m /mnt/secondary -u
> >
> http://download.cloud.com/templates/acton/acton-systemvm-02062012.qcow2.bz2
> > -h kvm -s <optional-management-server-secret-key> -F
> >
> >
> > Or should I be utilizing another?
> >
> > - Maurice
>
Re: System VM
Posted by Marcus Sorensen <sh...@gmail.com>.
For 4.2 that doesn't work. If the docs say that, we need to fix it.
On Wed, Oct 2, 2013 at 5:00 PM, Maurice Lawler <ma...@me.com> wrote:
> Hello,
>
> Going through the install, I noticed the system VM template hasnt changed
> URL. Is it safe to assume to utilize this one:
>
> # /usr/lib64/cloud/common/scripts/storage/secondary/cloud-install-sys-tmplt
> -m /mnt/secondary -u
> http://download.cloud.com/templates/acton/acton-systemvm-02062012.qcow2.bz2
> -h kvm -s <optional-management-server-secret-key> -F
>
>
> Or should I be utilizing another?
>
> - Maurice
Re: System VM
Posted by Maurice Lawler <ma...@me.com>.
Thank you!
- Maurice
On 10/2/13, 7:21 PM, Travis Graham wrote:
> Here are the correct links for 4.2.0:
>
> Xenserver : http://download.cloud.com/templates/4.2/systemvmtemplate-2013-07-12-master-xen.vhd.bz2
> KVM : http://download.cloud.com/templates/4.2/systemvmtemplate-2013-06-12-master-kvm.qcow2.bz2
> VMware : http://download.cloud.com/templates/4.2/systemvmtemplate-4.2-vh7.ova
>
> Travis
>
> On Oct 2, 2013, at 7:00 PM, Maurice Lawler <ma...@me.com> wrote:
>
>> Hello,
>>
>> Going through the install, I noticed the system VM template hasnt changed URL. Is it safe to assume to utilize this one:
>>
>> # /usr/lib64/cloud/common/scripts/storage/secondary/cloud-install-sys-tmplt -m /mnt/secondary -u http://download.cloud.com/templates/acton/acton-systemvm-02062012.qcow2.bz2 -h kvm -s <optional-management-server-secret-key> -F
>>
>>
>> Or should I be utilizing another?
>>
>> - Maurice
>
Re: System VM
Posted by Chiradeep Vittal <Ch...@citrix.com>.
I enabled cloudfront on this so that folks in
S.America/Africa/Europe/Asia/Oceania can have better speeds.
Just substitute d21ifhcun6b1t2.cloudfront.net for download.cloud.com
On 10/2/13 4:21 PM, "Travis Graham" <tg...@tgraham.us> wrote:
>Here are the correct links for 4.2.0:
>
>Xenserver :
>http://download.cloud.com/templates/4.2/systemvmtemplate-2013-07-12-master
>-xen.vhd.bz2
>KVM :
>http://download.cloud.com/templates/4.2/systemvmtemplate-2013-06-12-master
>-kvm.qcow2.bz2
>VMware :
>http://download.cloud.com/templates/4.2/systemvmtemplate-4.2-vh7.ova
>
>Travis
>
>On Oct 2, 2013, at 7:00 PM, Maurice Lawler <ma...@me.com> wrote:
>
>> Hello,
>>
>> Going through the install, I noticed the system VM template hasnt
>>changed URL. Is it safe to assume to utilize this one:
>>
>> #
>>/usr/lib64/cloud/common/scripts/storage/secondary/cloud-install-sys-tmplt
>> -m /mnt/secondary -u
>>http://download.cloud.com/templates/acton/acton-systemvm-02062012.qcow2.b
>>z2 -h kvm -s <optional-management-server-secret-key> -F
>>
>>
>> Or should I be utilizing another?
>>
>> - Maurice
>
Re: System VM
Posted by Travis Graham <tg...@tgraham.us>.
Here are the correct links for 4.2.0:
Xenserver : http://download.cloud.com/templates/4.2/systemvmtemplate-2013-07-12-master-xen.vhd.bz2
KVM : http://download.cloud.com/templates/4.2/systemvmtemplate-2013-06-12-master-kvm.qcow2.bz2
VMware : http://download.cloud.com/templates/4.2/systemvmtemplate-4.2-vh7.ova
Travis
On Oct 2, 2013, at 7:00 PM, Maurice Lawler <ma...@me.com> wrote:
> Hello,
>
> Going through the install, I noticed the system VM template hasnt changed URL. Is it safe to assume to utilize this one:
>
> # /usr/lib64/cloud/common/scripts/storage/secondary/cloud-install-sys-tmplt -m /mnt/secondary -u http://download.cloud.com/templates/acton/acton-systemvm-02062012.qcow2.bz2 -h kvm -s <optional-management-server-secret-key> -F
>
>
> Or should I be utilizing another?
>
> - Maurice