You are viewing a plain text version of this content. The canonical link for it is here.
Posted to marketing@cloudstack.apache.org by Arjan Eriks <AE...@schubergphilis.com> on 2016/01/31 22:30:54 UTC
Schuberg and the way forward
Hi all,
Over the last weeks we have had contact with a lot of you already. Most probably you are already aware of our (Schuberg Philis’s) plans moving forward.
As you know we are working hard to get faster releases and to get to that it means that we need to move to code commits that are fully tested, a master that never breaks and maybe evenly important to work towards some architectural changes in the code itself. For us it means that we forked the code after the latest release and we will work on that branch as of now. Of course we will remain active on porting back nasty bug fixes and such.
I would like to thanks each and every one of you. Without this OSS community we would not be where we are now. And that is that all our customers run in our Cloud. A Cloudstack cloud.
For those interested feel free to read my blog post about our move: https://www.cupfighter.net/2016/01/welcome-mission-critical-cloud. Or feel free to contact us directly. You now where to find us.
Cheers, Arjan
Re: Schuberg and the way forward
Posted by Nux! <nu...@li.nux.ro>.
Hi Arjan,
Good luck with CCloud and thanks. Hope to still see you guys around, I guess we'll be paying a lot of attention to your fork.
Lucian
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
----- Original Message -----
> From: "Arjan Eriks" <AE...@schubergphilis.com>
> To: marketing@cloudstack.apache.org
> Sent: Sunday, 31 January, 2016 21:30:54
> Subject: Schuberg and the way forward
> Hi all,
>
> Over the last weeks we have had contact with a lot of you already. Most probably
> you are already aware of our (Schuberg Philis’s) plans moving forward.
>
> As you know we are working hard to get faster releases and to get to that it
> means that we need to move to code commits that are fully tested, a master that
> never breaks and maybe evenly important to work towards some architectural
> changes in the code itself. For us it means that we forked the code after the
> latest release and we will work on that branch as of now. Of course we will
> remain active on porting back nasty bug fixes and such.
>
> I would like to thanks each and every one of you. Without this OSS community we
> would not be where we are now. And that is that all our customers run in our
> Cloud. A Cloudstack cloud.
>
> For those interested feel free to read my blog post about our move:
> https://www.cupfighter.net/2016/01/welcome-mission-critical-cloud. Or feel free
> to contact us directly. You now where to find us.
>
> Cheers, Arjan
Re: Schuberg and the way forward
Posted by Arjan Eriks <er...@gmail.com>.
Thanks Daan,
I really hope this move works out for all parties. It would be fun to be at
the same cloudstack events and such. The discussions, plans and the
community feel of cloudstack is one of the best i have experienced.
Regards, Arjan
On Mon, Feb 1, 2016 at 9:33 AM, Daan Hoogland <da...@gmail.com>
wrote:
> Arjan,
>
> I guess not even you and colleagues know how much off your involvement is
> sticking around. I feel you have been fun, productive and innovative so it
> is probably not going to be enough in my opinion. I wish more for your
> architectural changes then the nasty bug fixes but all are welcome. I
> salute you for what you are doing and for what you have done and hope to
> see you around.
>
> regards, Daan
>
> On Sun, Jan 31, 2016 at 10:30 PM, Arjan Eriks <AE...@schubergphilis.com>
> wrote:
>
>> Hi all,
>>
>> Over the last weeks we have had contact with a lot of you already. Most
>> probably you are already aware of our (Schuberg Philis’s) plans moving
>> forward.
>>
>> As you know we are working hard to get faster releases and to get to that
>> it means that we need to move to code commits that are fully tested, a
>> master that never breaks and maybe evenly important to work towards some
>> architectural changes in the code itself. For us it means that we forked
>> the code after the latest release and we will work on that branch as of
>> now. Of course we will remain active on porting back nasty bug fixes and
>> such.
>>
>> I would like to thanks each and every one of you. Without this OSS
>> community we would not be where we are now. And that is that all our
>> customers run in our Cloud. A Cloudstack cloud.
>>
>> For those interested feel free to read my blog post about our move:
>> https://www.cupfighter.net/2016/01/welcome-mission-critical-cloud. Or
>> feel free to contact us directly. You now where to find us.
>>
>> Cheers, Arjan
>>
>
>
>
> --
> Daan
>
Re: Schuberg and the way forward
Posted by Daan Hoogland <da...@gmail.com>.
Arjan,
I guess not even you and colleagues know how much off your involvement is
sticking around. I feel you have been fun, productive and innovative so it
is probably not going to be enough in my opinion. I wish more for your
architectural changes then the nasty bug fixes but all are welcome. I
salute you for what you are doing and for what you have done and hope to
see you around.
regards, Daan
On Sun, Jan 31, 2016 at 10:30 PM, Arjan Eriks <AE...@schubergphilis.com>
wrote:
> Hi all,
>
> Over the last weeks we have had contact with a lot of you already. Most
> probably you are already aware of our (Schuberg Philis’s) plans moving
> forward.
>
> As you know we are working hard to get faster releases and to get to that
> it means that we need to move to code commits that are fully tested, a
> master that never breaks and maybe evenly important to work towards some
> architectural changes in the code itself. For us it means that we forked
> the code after the latest release and we will work on that branch as of
> now. Of course we will remain active on porting back nasty bug fixes and
> such.
>
> I would like to thanks each and every one of you. Without this OSS
> community we would not be where we are now. And that is that all our
> customers run in our Cloud. A Cloudstack cloud.
>
> For those interested feel free to read my blog post about our move:
> https://www.cupfighter.net/2016/01/welcome-mission-critical-cloud. Or
> feel free to contact us directly. You now where to find us.
>
> Cheers, Arjan
>
--
Daan
Re: Schuberg and the way forward
Posted by Ian Rae <ir...@cloudops.com>.
Arjan, thanks for sharing, to me this is an indication of a healthy and
diverse ecosystem meeting multiple needs and it is an excellent sign for
the greater Apache CloudStack that a key use case is to deliver
mission-critical cloud services!
On Monday, February 1, 2016, Arjan Eriks <er...@gmail.com> wrote:
> Erik, Daan,
>
> The details on how we exactly work with PR is probably not best for the
> marketing List. But we of course will try to see if they will fit in
> CloudStack as well. You are right that this is probably where the diverge
> begins.
>
> So far the press is low key on the move. Only this blogpost is out there,
> and it is positive for both CloudStack and SBP.
> http://www.networkworld.com/article/3028065/hybrid-cloud/schuberg-philis-forks-cloudstack-what-happens-next.html#tk.rss_all
>
> I will stop spamming this marketing list now. If you do have more
> questions, please mail us directly. Lets keep this channel for the
> marketing of CloudStack!
>
> Regards,
>
> Arjan
>
> On Mon, Feb 1, 2016 at 11:46 AM, Daan Hoogland <daan.hoogland@gmail.com
> <javascript:_e(%7B%7D,'cvml','daan.hoogland@gmail.com');>> wrote:
>
>> Yes, Erik. I hope they do too.
>>
>> Biligual auto correct use. Read at your own risico
>> Op 1 feb. 2016 10:57 AM schreef "Erik Weber" <terbolous@gmail.com
>> <javascript:_e(%7B%7D,'cvml','terbolous@gmail.com');>>:
>>
>>> On Sun, Jan 31, 2016 at 10:30 PM, Arjan Eriks <AEriks@schubergphilis.com
>>> <javascript:_e(%7B%7D,'cvml','AEriks@schubergphilis.com');>> wrote:
>>>
>>>> Hi all,
>>>>
>>>> Over the last weeks we have had contact with a lot of you already. Most
>>>> probably you are already aware of our (Schuberg Philis’s) plans moving
>>>> forward.
>>>>
>>>> As you know we are working hard to get faster releases and to get to
>>>> that it means that we need to move to code commits that are fully tested, a
>>>> master that never breaks and maybe evenly important to work towards some
>>>> architectural changes in the code itself. For us it means that we forked
>>>> the code after the latest release and we will work on that branch as of
>>>> now. Of course we will remain active on porting back nasty bug fixes and
>>>> such.
>>>>
>>>> I would like to thanks each and every one of you. Without this OSS
>>>> community we would not be where we are now. And that is that all our
>>>> customers run in our Cloud. A Cloudstack cloud.
>>>>
>>>> For those interested feel free to read my blog post about our move:
>>>> https://www.cupfighter.net/2016/01/welcome-mission-critical-cloud. Or
>>>> feel free to contact us directly. You now where to find us.
>>>>
>>>>
>>> Not sure what I really feel at the moment, it is probably not suited for
>>> publication.
>>>
>>> I do feel that this should be published broader than just on the
>>> marketing list.
>>>
>>> But I hope you could take the time to PR your fundamental changes, so
>>> that cosmic and cloudstack doesn't diverge too much.
>>>
>>> --
>>> Erik
>>>
>>>>
>>>
>
--
Ian Rae
CEO | PDG
c: 514.944.4008
CloudOps | Cloud Infrastructure and Networking Solutions
www.cloudops.com | 420 rue Guy | Montreal | Canada | H3J 1S6
RE: Schuberg and the way forward
Posted by Samir Agarwal <sa...@accelerite.com>.
Arjan,
From everything I have been told in my brief association with CloudStack/CloudPlatform, you and Schuberg Philis have been awesome citizens of this community. I understand your drivers to move more rapidly. I am hopeful that you will continue to make contributions back to CloudStack by way of bug fixes and feature additions, rather than go on a path of complete diversion. Is that what you intend to do?
Regards
Samir
From: Arjan Eriks [mailto:eriarjan@gmail.com]
Sent: Monday, February 01, 2016 12:57 PM
To: marketing@cloudstack.apache.org
Subject: Re: Schuberg and the way forward
Erik, Daan,
The details on how we exactly work with PR is probably not best for the marketing List. But we of course will try to see if they will fit in CloudStack as well. You are right that this is probably where the diverge begins.
So far the press is low key on the move. Only this blogpost is out there, and it is positive for both CloudStack and SBP. http://www.networkworld.com/article/3028065/hybrid-cloud/schuberg-philis-forks-cloudstack-what-happens-next.html#tk.rss_all
I will stop spamming this marketing list now. If you do have more questions, please mail us directly. Lets keep this channel for the marketing of CloudStack!
Regards,
Arjan
On Mon, Feb 1, 2016 at 11:46 AM, Daan Hoogland <da...@gmail.com>> wrote:
Yes, Erik. I hope they do too.
Biligual auto correct use. Read at your own risico
Op 1 feb. 2016 10:57 AM schreef "Erik Weber" <te...@gmail.com>>:
On Sun, Jan 31, 2016 at 10:30 PM, Arjan Eriks <AE...@schubergphilis.com>> wrote:
Hi all,
Over the last weeks we have had contact with a lot of you already. Most probably you are already aware of our (Schuberg Philis’s) plans moving forward.
As you know we are working hard to get faster releases and to get to that it means that we need to move to code commits that are fully tested, a master that never breaks and maybe evenly important to work towards some architectural changes in the code itself. For us it means that we forked the code after the latest release and we will work on that branch as of now. Of course we will remain active on porting back nasty bug fixes and such.
I would like to thanks each and every one of you. Without this OSS community we would not be where we are now. And that is that all our customers run in our Cloud. A Cloudstack cloud.
For those interested feel free to read my blog post about our move: https://www.cupfighter.net/2016/01/welcome-mission-critical-cloud. Or feel free to contact us directly. You now where to find us.
Not sure what I really feel at the moment, it is probably not suited for publication.
I do feel that this should be published broader than just on the marketing list.
But I hope you could take the time to PR your fundamental changes, so that cosmic and cloudstack doesn't diverge too much.
--
Erik
DISCLAIMER
==========
This e-mail may contain privileged and confidential information which is the property of Accelerite, a Persistent Systems business. It is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorized to read, retain, copy, print, distribute or use this message. If you have received this communication in error, please notify the sender and delete all copies of this message. Accelerite, a Persistent Systems business does not accept any liability for virus infected mails.
Re: Schuberg and the way forward
Posted by Arjan Eriks <er...@gmail.com>.
Erik, Daan,
The details on how we exactly work with PR is probably not best for the
marketing List. But we of course will try to see if they will fit in
CloudStack as well. You are right that this is probably where the diverge
begins.
So far the press is low key on the move. Only this blogpost is out there,
and it is positive for both CloudStack and SBP.
http://www.networkworld.com/article/3028065/hybrid-cloud/schuberg-philis-forks-cloudstack-what-happens-next.html#tk.rss_all
I will stop spamming this marketing list now. If you do have more
questions, please mail us directly. Lets keep this channel for the
marketing of CloudStack!
Regards,
Arjan
On Mon, Feb 1, 2016 at 11:46 AM, Daan Hoogland <da...@gmail.com>
wrote:
> Yes, Erik. I hope they do too.
>
> Biligual auto correct use. Read at your own risico
> Op 1 feb. 2016 10:57 AM schreef "Erik Weber" <te...@gmail.com>:
>
>> On Sun, Jan 31, 2016 at 10:30 PM, Arjan Eriks <AE...@schubergphilis.com>
>> wrote:
>>
>>> Hi all,
>>>
>>> Over the last weeks we have had contact with a lot of you already. Most
>>> probably you are already aware of our (Schuberg Philis’s) plans moving
>>> forward.
>>>
>>> As you know we are working hard to get faster releases and to get to
>>> that it means that we need to move to code commits that are fully tested, a
>>> master that never breaks and maybe evenly important to work towards some
>>> architectural changes in the code itself. For us it means that we forked
>>> the code after the latest release and we will work on that branch as of
>>> now. Of course we will remain active on porting back nasty bug fixes and
>>> such.
>>>
>>> I would like to thanks each and every one of you. Without this OSS
>>> community we would not be where we are now. And that is that all our
>>> customers run in our Cloud. A Cloudstack cloud.
>>>
>>> For those interested feel free to read my blog post about our move:
>>> https://www.cupfighter.net/2016/01/welcome-mission-critical-cloud. Or
>>> feel free to contact us directly. You now where to find us.
>>>
>>>
>> Not sure what I really feel at the moment, it is probably not suited for
>> publication.
>>
>> I do feel that this should be published broader than just on the
>> marketing list.
>>
>> But I hope you could take the time to PR your fundamental changes, so
>> that cosmic and cloudstack doesn't diverge too much.
>>
>> --
>> Erik
>>
>>>
>>
Re: Schuberg and the way forward
Posted by Daan Hoogland <da...@gmail.com>.
Yes, Erik. I hope they do too.
Biligual auto correct use. Read at your own risico
Op 1 feb. 2016 10:57 AM schreef "Erik Weber" <te...@gmail.com>:
> On Sun, Jan 31, 2016 at 10:30 PM, Arjan Eriks <AE...@schubergphilis.com>
> wrote:
>
>> Hi all,
>>
>> Over the last weeks we have had contact with a lot of you already. Most
>> probably you are already aware of our (Schuberg Philis’s) plans moving
>> forward.
>>
>> As you know we are working hard to get faster releases and to get to that
>> it means that we need to move to code commits that are fully tested, a
>> master that never breaks and maybe evenly important to work towards some
>> architectural changes in the code itself. For us it means that we forked
>> the code after the latest release and we will work on that branch as of
>> now. Of course we will remain active on porting back nasty bug fixes and
>> such.
>>
>> I would like to thanks each and every one of you. Without this OSS
>> community we would not be where we are now. And that is that all our
>> customers run in our Cloud. A Cloudstack cloud.
>>
>> For those interested feel free to read my blog post about our move:
>> https://www.cupfighter.net/2016/01/welcome-mission-critical-cloud. Or
>> feel free to contact us directly. You now where to find us.
>>
>>
> Not sure what I really feel at the moment, it is probably not suited for
> publication.
>
> I do feel that this should be published broader than just on the marketing
> list.
>
> But I hope you could take the time to PR your fundamental changes, so that
> cosmic and cloudstack doesn't diverge too much.
>
> --
> Erik
>
>>
>
Re: Schuberg and the way forward
Posted by Erik Weber <te...@gmail.com>.
On Sun, Jan 31, 2016 at 10:30 PM, Arjan Eriks <AE...@schubergphilis.com>
wrote:
> Hi all,
>
> Over the last weeks we have had contact with a lot of you already. Most
> probably you are already aware of our (Schuberg Philis’s) plans moving
> forward.
>
> As you know we are working hard to get faster releases and to get to that
> it means that we need to move to code commits that are fully tested, a
> master that never breaks and maybe evenly important to work towards some
> architectural changes in the code itself. For us it means that we forked
> the code after the latest release and we will work on that branch as of
> now. Of course we will remain active on porting back nasty bug fixes and
> such.
>
> I would like to thanks each and every one of you. Without this OSS
> community we would not be where we are now. And that is that all our
> customers run in our Cloud. A Cloudstack cloud.
>
> For those interested feel free to read my blog post about our move:
> https://www.cupfighter.net/2016/01/welcome-mission-critical-cloud. Or
> feel free to contact us directly. You now where to find us.
>
>
Not sure what I really feel at the moment, it is probably not suited for
publication.
I do feel that this should be published broader than just on the marketing
list.
But I hope you could take the time to PR your fundamental changes, so that
cosmic and cloudstack doesn't diverge too much.
--
Erik
>