tl;dr I want to move devcloud4 into some community location, where
should I put it?
Hi all,
As previously discussed on the list awhile back I'm wanting to move
the devcloud4[1] stuff into more of a primary view and out of a public
repository that is just hosted on my personal github account. I ha
> On Apr 8, 2015, at 7:32 AM, Ian Duffy wrote:
>
> tl;dr I want to move devcloud4 into some community location, where
> should I put it?
our repo :)
>
> Hi all,
>
> As previously discussed on the list awhile back I'm wanting to move
> the devcloud4[1] stuff into more of a primary view and ou
Hi Ian,
On Wednesday 08 April 2015 11:02 AM, Ian Duffy wrote:
tl;dr I want to move devcloud4 into some community location, where
should I put it?
If you need to host the readymade DevCloud4 disk images, I can help host
it on packages.shapeblue.com which can be also mirrored by Lucian.
Hi all
> If you need to host the readymade DevCloud4 disk images, I can help host
it on packages.shapeblue.com which can be also mirrored by Lucian.
Thanks but I got this covered. All images are hosted on S3 and shared
via vagrant-cloud which makes them very easy to import. The question
refers to the "co
Awesome! Thanks for the feedback all.
I've started to bring over the stuff on my own fork
https://github.com/imduffy15/cloudstack/commit/08f1cef3d0e5fae85bb5312c7b7c1c82d3e4c7e1
Need to add in the apache licenses everywhere and I wish to test
everything again (its been awhile).
Expect a PR over
>
> Preferably, I'd feel safer to go /tools/devcloud4. We can discuss
> cleaning up at a later point and move things about accordingly? (Yes I
> am totally just problem avoiding here)
>
I agree to this. lets merge it to tools/devcloud4 and then after some
testing/feedback, start cleaning the rest.
> On Apr 8, 2015, at 3:48 PM, Ian Duffy wrote:
>
>> If you need to host the readymade DevCloud4 disk images, I can help host
> it on packages.shapeblue.com which can be also mirrored by Lucian.
>
> Thanks but I got this covered. All images are hosted on S3 and shared
> via vagrant-cloud which m
