CloudStack 4.11 adoption/vendors map

[Ivan Kudryavtsev]

After the "Why CloudStack 5" I decided to put some efforts to build the map
for CloudStack infrastructure and would like to present the initial map for
CS 4.11.2 world:
https://raw.githubusercontent.com/bwsw/cloudstack-map/master/topologies.png

What I would like to offer to the community is explained below:
We (Bitworks) are ready to dedicate a technical writer from our team who
can actualize and publish actualized map for the community. That person
will handle incoming requests for inclusion in the form which can be mapped
into the diagram and publish the diagram back to GitHub and maybe we can
push it to CS documentation when it's ready.

The purpose of it is to help:
1. Find what is used and what is not and is the subject for the removal.
2. What topology has a vendor and users behind it, who can help with it.
3. What serious problems exist in certain deployment mode.
4. New adopters onboarding.
5. Understand the development capacity of the community.
6. Understand what users are interested in.

What you can do:
Send the report which includes what you use to the:
- Github Issue https://github.com/bwsw/cloudstack-map
- E-mail: cloudst...@bw-sw.com
- Google Form: https://goo.gl/forms/eMFEaxbfyCAFF0rj1
if you would like to keep the privacy.

The report should include the description of Storage, Hypervisor,
Networking topology, known bugs, etc. Take a look at the form:
https://goo.gl/forms/eMFEaxbfyCAFF0rj1

Our engineer will update the picture every time when you send something.
Also, we generate the document with expectations from the users who shared
something and publish it to the community.

Please feel free to advise and improve the work. On the March, 1st we
release a summary about the work which will help to understand the integral
results and community expectations.

-- 
With best regards, Ivan Kudryavtsev
Bitworks LLC
Cell RU: +7-923-414-1515
Cell USA: +1-201-257-1512
WWW: http://bitworks.software/ 

Re: Why CloudStack 5

[Ivan Kudryavtsev]

Well, my intention is to prevent the community from doing revolutionary
changes intending to deliver redesigned 5.0, to keep going the current road
improving the codebase, removing the odd stuff like 'Citrix NetScaler',
'Juniper XYZ' if nobody supports them, improving current functionality and
adding new core features which are opensource without vendor lock-in, e.g.
SDNs (I know Wido is very into it) e.g. Cumulus infra support. I believe
current codebase is a pretty capable basement for future stable
functionality.

About new UI, etc stuff... Let's be honest. We develop CloudStack-UI
project for 1.5 years AFAIK. No single PR from other developers. Next,
Imagine, you have tree dedicated devs for CS5.X. Ok, it will take two years
to deliver new UI. Is it possible? NO.

Only gradual improvement can work for the current production team. We need
to put efforts to broaden the community, delivering the stuff which
helps new adopters to launch fast, e.g. as simple as Proxmox VE or oVirt or
VmWare ESXi. New users don't need much top-notch stuff, they need to
bootstrap fast.




сб, 26 янв. 2019 г. в 04:26, Rafael Weingärtner :

> I am 100% with @Rohit Yadav  with respect to
> 4.12. I do diverge regarding the next LTS version though.
>
> As you all guys said, the community is small, and as such, if we have the
> requirement for multiple major changes, before upgrading the "X" bit in a
> release, we will never go there (that is a fact). In my opinion, because
> the community is small, we should look for a single major change (e.g. new
> database upgrade method/scheme), and this should trigger the next major
> release. The ability to upgrade the "X" bit free us to remove things such
> as the basic network support (of course, we need to create a migration
> path), new database scheme management method, normalize log messages and
> logging framework and so on (many more issues can be listed here).
>
> I really do not understand why we have so much resistance from some people
> on this topic.
>
> On Thu, Jan 24, 2019 at 2:27 PM Suresh Kumar Anaparti <
> sureshkumar.anapa...@gmail.com> wrote:
>
> > Sounds good. Altogether, the makeover should be a new user experience and
> > leverage the latest hypervisor/storage tech and new/redesigned
> frameworks.
> >
> > -Suresh
> >
> > On Thu, Jan 24, 2019 at 10:13 AM Rohit Yadav 
> > wrote:
> >
> > > I'm in the favour of keeping the 4.x going because no API compatibility
> > is
> > > broken, and as long as we are following semver there is no need.
> Calling
> > a
> > > 4.x a 5.x just for the sake of bumping versions may cause some
> perception
> > > issue.
> > >
> > > Removal of unsupported/poc/incomplete features, plugins including APIs
> > > should not constitute breaking of compatibility. Several network and
> > > hypervisor plugins are still in poc/incomplete/unmaintained state.
> > >
> > > Unless the API layer, and perhaps DB layer is re-architected there is
> no
> > > point in calling the next version 5.x as long as semver is followed.
> > >
> > > In my opinion, the next major version 5.0 should have a restful
> versioned
> > > API layer, a new DB+upgrade framework that may support multiple db
> > servers,
> > > a new UI, sandboxed plugin framework (right now a plugin can do
> anything
> > it
> > > wants to say the cloud db), a new agent-clustering framework (the
> current
> > > low level nio and rpc code goes away), a distributed message bus and
> > > locking service (that we thought to introduce in 4.2,4.3 but
> incomplete),
> > > and refactor the networking/VR layer with a new VR. Not to mention
> > cleanup
> > > some technical debt. The keywords being major architectural and
> > > api/integrational changes. Some of this maybe on-going, but we'll get
> to
> > > 5.x with patience over time.
> > >
> > > Regards,
> > > Rohit Yadav
> > >
> > > 
> > > From: Ivan Kudryavtsev 
> > > Sent: Tuesday, January 22, 2019 9:15:29 AM
> > > To: users; dev
> > > Subject: Why CloudStack 5
> > >
> > > I decided whether to write it several weeks thinking about the stones
> and
> > > rotten potatoes, but still decided to do that. Hope it will not raise
> the
> > > stress level.
> > >
> > > Colleagues and ACS leaders, I would like to initiate the discussion.
> Why
> > go
> > > to CS5 rather than stay with 4.XX. Some thoughts are:
> > >
> > > 1. According to the versioning guide, the first number stands for
> radical
> > > changes like if the community decided to go from current ORM to
> > Hibernate.
> > > I don't see the capabilities for such changes and there are no
> intentions
> > > for the implementation.
> > >
> > > 2. I can realize that we 'stuck' with '4.XX' and the marketing can be
> > > disappointing from that point of view. Then, OK, let's just skip the
> > first
> > > number "4." and release, ACS 13.X, 14.X, 15.X and so on. Every version
> > will
> > > receive new impressing version number and everyone could be happy about
> > > that.
> > >
> > > Going 

Re: Why CloudStack 5

[Rafael Weingärtner]

I am 100% with @Rohit Yadav  with respect to
4.12. I do diverge regarding the next LTS version though.

As you all guys said, the community is small, and as such, if we have the
requirement for multiple major changes, before upgrading the "X" bit in a
release, we will never go there (that is a fact). In my opinion, because
the community is small, we should look for a single major change (e.g. new
database upgrade method/scheme), and this should trigger the next major
release. The ability to upgrade the "X" bit free us to remove things such
as the basic network support (of course, we need to create a migration
path), new database scheme management method, normalize log messages and
logging framework and so on (many more issues can be listed here).

I really do not understand why we have so much resistance from some people
on this topic.

On Thu, Jan 24, 2019 at 2:27 PM Suresh Kumar Anaparti <
sureshkumar.anapa...@gmail.com> wrote:

> Sounds good. Altogether, the makeover should be a new user experience and
> leverage the latest hypervisor/storage tech and new/redesigned frameworks.
>
> -Suresh
>
> On Thu, Jan 24, 2019 at 10:13 AM Rohit Yadav 
> wrote:
>
> > I'm in the favour of keeping the 4.x going because no API compatibility
> is
> > broken, and as long as we are following semver there is no need. Calling
> a
> > 4.x a 5.x just for the sake of bumping versions may cause some perception
> > issue.
> >
> > Removal of unsupported/poc/incomplete features, plugins including APIs
> > should not constitute breaking of compatibility. Several network and
> > hypervisor plugins are still in poc/incomplete/unmaintained state.
> >
> > Unless the API layer, and perhaps DB layer is re-architected there is no
> > point in calling the next version 5.x as long as semver is followed.
> >
> > In my opinion, the next major version 5.0 should have a restful versioned
> > API layer, a new DB+upgrade framework that may support multiple db
> servers,
> > a new UI, sandboxed plugin framework (right now a plugin can do anything
> it
> > wants to say the cloud db), a new agent-clustering framework (the current
> > low level nio and rpc code goes away), a distributed message bus and
> > locking service (that we thought to introduce in 4.2,4.3 but incomplete),
> > and refactor the networking/VR layer with a new VR. Not to mention
> cleanup
> > some technical debt. The keywords being major architectural and
> > api/integrational changes. Some of this maybe on-going, but we'll get to
> > 5.x with patience over time.
> >
> > Regards,
> > Rohit Yadav
> >
> > 
> > From: Ivan Kudryavtsev 
> > Sent: Tuesday, January 22, 2019 9:15:29 AM
> > To: users; dev
> > Subject: Why CloudStack 5
> >
> > I decided whether to write it several weeks thinking about the stones and
> > rotten potatoes, but still decided to do that. Hope it will not raise the
> > stress level.
> >
> > Colleagues and ACS leaders, I would like to initiate the discussion. Why
> go
> > to CS5 rather than stay with 4.XX. Some thoughts are:
> >
> > 1. According to the versioning guide, the first number stands for radical
> > changes like if the community decided to go from current ORM to
> Hibernate.
> > I don't see the capabilities for such changes and there are no intentions
> > for the implementation.
> >
> > 2. I can realize that we 'stuck' with '4.XX' and the marketing can be
> > disappointing from that point of view. Then, OK, let's just skip the
> first
> > number "4." and release, ACS 13.X, 14.X, 15.X and so on. Every version
> will
> > receive new impressing version number and everyone could be happy about
> > that.
> >
> > Going to version "5" currently looks like as an intention to refresh but
> > with very poor motivation. At least to me.
> >
> > The discussion is strongly welcome.
> >
> >
> >
> > --
> > With best regards, Ivan Kudryavtsev
> > Bitworks LLC
> > Cell RU: +7-923-414-1515
> > Cell USA: +1-201-257-1512
> > WWW: http://bitworks.software/ 
> >
> > rohit.ya...@shapeblue.com
> > www.shapeblue.com
> > Amadeus House, Floral Street, London  WC2E 9DPUK
> > @shapeblue
> >
> >
> >
> >
>


-- 
Rafael Weingärtner

Re: Dropping Nuage Networks support

[Wei ZHOU]

Hi Kris,

It was nice to meet you some times and see your contributions to the
project. Thank you and your colleagues for all your hard work.

All the best in the future !

-Wei


Kris Sterckx  于2019年1月25日周五 下午7:14写道：

> Folks,
>
>
>
> A management decision within Nuage Networks / Nokia has been made for
> dropping CloudStack support in the upcoming release.
>
> With that, we have been working at a clean cut, taking out Nuage SDN
> support from the code, as the last thing we want would be leaving
> unsupported/broken code in the repo. Obviously, all generically applicable
> contributions remain – only the Nuage specifics are taken out. Some of
> these generic contributions include per-NIC extra DHCP options support,
> extended Config Drive support (both discussed at the Miami CCC) and
> Physical Network Migration (presented at the last Montreal CCC).
>
> The following PR has been uploaded, pending your review:
>
>
> https://github.com/apache/cloudstack/pull/3146
>
>
>
> Together with Frank and Raf, I would like to thank everyone for the great
> collaboration, the time we spent at conferences/meetups and the overall joy
> we had. And I hope our ways to further cross.
>
> Keep up the great work.
>
>
>
> Kris
>

[GitHub] skattoju4 commented on a change in pull request #24: added updated instructions for ubuntu 18.04 and cloudstack 4.11

[GitBox]

skattoju4 commented on a change in pull request #24: added updated instructions 
for ubuntu 18.04 and cloudstack 4.11
URL: 
https://github.com/apache/cloudstack-documentation/pull/24#discussion_r251124562
 
 

 ##
 File path: source/developersguide/developer_guide.rst
 ##
 @@ -122,6 +123,79 @@ Finally install ``mkisofs`` with:
 
apt-get install genisoimage
 
+On Ubuntu 18.04
+~~~
+
+Run apt-get update to fetch the latest package list from the repo
+
+::
+
+   apt-get update
+
+NTP might already be installed, check it with ``service ntp status``. If
+it's not then install NTP to synchronize the clocks:
+
+::
+
+   apt-get install openntpd
+
+Install ``openjdk``. As we're using Linux, OpenJDK is our first choice.
+
+::
+
+   apt-get install openjdk-8-jdk
+
+Install ``tomcat8``
+
+::
+
+   apt-get install tomcat8
 
 Review comment:
   Thanks for pointing it out removed the tomcat step.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Re: Dropping Nuage Networks support

[Simon Weller]

Kris,


I echo what Rohit said. You've all been great to work with and we're going to 
miss your involvement in the community.

I wish you all the best and I hope we can all cross paths again in the future.


- Si


From: Rohit Yadav 
Sent: Friday, January 25, 2019 2:02 PM
To: dev@cloudstack.apache.org
Subject: Re: Dropping Nuage Networks support

Hi Kris, Frank and Raf,


It's unfortunate to read about the decision but I understand your position. I 
would like to thank you, Frank and Raf for your contribution, professionalism, 
participation in the community and the quality of contribution. With your final 
effort to do a proper cleanup with the PR you've set a new standard for other 
vendors and contributors to follow, something we've not seen in the community 
before and is highly appreciated. For that, I thank you all again.


It was a pleasure to work with you all. Good luck in your future projects, 
cheers!


Regards,

Rohit Yadav






From: Kris Sterckx 
Sent: Friday, January 25, 2019 11:44:04 PM
To: dev@cloudstack.apache.org
Subject: Dropping Nuage Networks support

Folks,



A management decision within Nuage Networks / Nokia has been made for
dropping CloudStack support in the upcoming release.

With that, we have been working at a clean cut, taking out Nuage SDN
support from the code, as the last thing we want would be leaving
unsupported/broken code in the repo. Obviously, all generically applicable
contributions remain – only the Nuage specifics are taken out. Some of
these generic contributions include per-NIC extra DHCP options support,
extended Config Drive support (both discussed at the Miami CCC) and
Physical Network Migration (presented at the last Montreal CCC).

The following PR has been uploaded, pending your review:


https://github.com/apache/cloudstack/pull/3146



Together with Frank and Raf, I would like to thank everyone for the great
collaboration, the time we spent at conferences/meetups and the overall joy
we had. And I hope our ways to further cross.

Keep up the great work.



Kris

rohit.ya...@shapeblue.com
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue

Re: Dropping Nuage Networks support

[Rohit Yadav]

Hi Kris, Frank and Raf,


It's unfortunate to read about the decision but I understand your position. I 
would like to thank you, Frank and Raf for your contribution, professionalism, 
participation in the community and the quality of contribution. With your final 
effort to do a proper cleanup with the PR you've set a new standard for other 
vendors and contributors to follow, something we've not seen in the community 
before and is highly appreciated. For that, I thank you all again.


It was a pleasure to work with you all. Good luck in your future projects, 
cheers!


Regards,

Rohit Yadav






From: Kris Sterckx 
Sent: Friday, January 25, 2019 11:44:04 PM
To: dev@cloudstack.apache.org
Subject: Dropping Nuage Networks support

Folks,



A management decision within Nuage Networks / Nokia has been made for
dropping CloudStack support in the upcoming release.

With that, we have been working at a clean cut, taking out Nuage SDN
support from the code, as the last thing we want would be leaving
unsupported/broken code in the repo. Obviously, all generically applicable
contributions remain – only the Nuage specifics are taken out. Some of
these generic contributions include per-NIC extra DHCP options support,
extended Config Drive support (both discussed at the Miami CCC) and
Physical Network Migration (presented at the last Montreal CCC).

The following PR has been uploaded, pending your review:


https://github.com/apache/cloudstack/pull/3146



Together with Frank and Raf, I would like to thank everyone for the great
collaboration, the time we spent at conferences/meetups and the overall joy
we had. And I hope our ways to further cross.

Keep up the great work.



Kris

rohit.ya...@shapeblue.com 
www.shapeblue.com
Amadeus House, Floral Street, London  WC2E 9DPUK
@shapeblue
  
 

Dropping Nuage Networks support

[Kris Sterckx]

Folks,



A management decision within Nuage Networks / Nokia has been made for
dropping CloudStack support in the upcoming release.

With that, we have been working at a clean cut, taking out Nuage SDN
support from the code, as the last thing we want would be leaving
unsupported/broken code in the repo. Obviously, all generically applicable
contributions remain – only the Nuage specifics are taken out. Some of
these generic contributions include per-NIC extra DHCP options support,
extended Config Drive support (both discussed at the Miami CCC) and
Physical Network Migration (presented at the last Montreal CCC).

The following PR has been uploaded, pending your review:


https://github.com/apache/cloudstack/pull/3146



Together with Frank and Raf, I would like to thank everyone for the great
collaboration, the time we spent at conferences/meetups and the overall joy
we had. And I hope our ways to further cross.

Keep up the great work.



Kris

[GitHub] rhtyd commented on issue #26: installdocs: docs for https/ssl and TLS security configuration

[GitBox]

rhtyd commented on issue #26: installdocs: docs for https/ssl and TLS security 
configuration
URL: 
https://github.com/apache/cloudstack-documentation/pull/26#issuecomment-457648380
 
 
   @andrijapanic @DagSonsteboSB - please review as well


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] rhtyd opened a new pull request #26: installdocs: docs for https/ssl and TLS security configuration

[GitBox]

rhtyd opened a new pull request #26: installdocs: docs for https/ssl and TLS 
security configuration
URL: https://github.com/apache/cloudstack-documentation/pull/26
 
 
   This fixed old tomcat ssl docs with Jetty/server.properties docs and adds 
section on disabling old/vulnerable TLS algorithms for JRE.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] rhtyd commented on a change in pull request #24: added updated instructions for ubuntu 18.04 and cloudstack 4.11

[GitBox]

rhtyd commented on a change in pull request #24: added updated instructions for 
ubuntu 18.04 and cloudstack 4.11
URL: 
https://github.com/apache/cloudstack-documentation/pull/24#discussion_r251056504
 
 

 ##
 File path: source/developersguide/developer_guide.rst
 ##
 @@ -122,6 +123,79 @@ Finally install ``mkisofs`` with:
 
apt-get install genisoimage
 
+On Ubuntu 18.04
+~~~
+
+Run apt-get update to fetch the latest package list from the repo
+
+::
+
+   apt-get update
+
+NTP might already be installed, check it with ``service ntp status``. If
+it's not then install NTP to synchronize the clocks:
+
+::
+
+   apt-get install openntpd
+
+Install ``openjdk``. As we're using Linux, OpenJDK is our first choice.
+
+::
+
+   apt-get install openjdk-8-jdk
+
+Install ``tomcat8``
+
+::
+
+   apt-get install tomcat8
 
 Review comment:
   This is old/deprecated, we don't need tomcat anymore.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] rhtyd merged pull request #22: Update requirements for Ubuntu 18.04

[GitBox]

rhtyd merged pull request #22: Update requirements for Ubuntu 18.04
URL: https://github.com/apache/cloudstack-documentation/pull/22
 
 
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services