I have been using Linux and the Internet since the mid 1990s.
There are still 3 consecutively numbered C class registered to me for
different clients back in the days when c-class networks were given out
from massive ranges of free numbers.
I have set up small ISP operations for clients with multiple domains
including web sites, e-mail servers, fileservers, etc.
I have done this on SCO , Mandrake, CentOS 4 to 7.
I should not have to struggle to figure out how set up Cloudstack in a
small configuration with a few servers and a single public IP.
The documentation on networking is jumbled about and so unclear that I
can only point out why it is not clear but can not figure out the truth
sufficiently well to actually fix it.
I still don't know where the sources for the drawings are kept even
though I have asked several times.
It needs a team approach with someone who knows the truth and someone
who can write it down so that someone who did not write the code can
figure out what to do.
The biggest problem with programmers writing the user documentation is
that they are so caught up in the exceptions and special cases.
They spent a lot of time figuring out how to handle these oddball cases
that they feel that these triumphs must be on the front page.
They forget to explain the 95% case and lace the description of the main
flow with notes about these interesting exceptions.
That is not just true for Cloudstack but is a general problem with
documentation just because we are all human.
They also forget that the user does not want to be an expert in the
topic but wants to know enough to get the thing running.
The user has a lot of other problems and does not to become a developer
in order to get this to work.
In my case, I really need to get some internal applications (accounting,
SCM, issue tracking, Maven repo, 20 web sites etc.) running on virtual
machines in an environment that is easy to manage. I want to support
clients who I am supporting as users of other systems - just want simple
low volume services to support my supporting of their users.
I only expect to have 4 servers, one NIC per machine to support 1
transaction per second on a busy day
I may get down to 2 servers if Cloudstack works well and allows me to
manage test servers and run docker nicely.
I do not want to know enough to be the network administrator at Google
or Amazon.
This should not be hard to implement and from what I have seen it is not
but the networking docs are a major barrier to acceptance by mid-market
companies - 300-1000 users with 1 or 2 System Admins who have to support
all of the operations requirements and help developers and application
support teams test and keep production systems running.
Ron
On 03/03/2016 6:22 AM, Mario Giammarco wrote:
Simon Weller <sweller@...> writes:
I do agree that the docs are confusing, especially if you have a limited
knowledge of networking concepts.
In terms of the complexity, a lot of that has to do with the fact that
every company has different service
requirements and ACS needs to be flexible enough to accommodate very
different underlying needs.
Not agree. Even with good knowledge documentation is confusing because:
- it assumes you are always in the use case of "I have plenty of routable ips"
- it forgets to say that two system vms are create to manage routing and
secondary storage
- it does not say that cloudstack manager can rewrite your host configuration
It's always best to start with a basic zone, unless you REALLY need some
functionality within an advanced
zone. As soon as you move into advanced zone networking, you need to have
a good understanding of layer 2/3
networking.
I was able to make my cloudstack network working only when I skipped basic
zone and used advanced zone
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
